Monday, 2017-03-20

*** crushil has joined #openstack-kolla00:00
*** crushil has quit IRC00:03
*** crushil has joined #openstack-kolla00:03
*** crushil has quit IRC00:06
*** crushil has joined #openstack-kolla00:07
*** crushil has quit IRC00:10
*** crushil has joined #openstack-kolla00:10
*** crushil has quit IRC00:13
*** dave-mccowan has joined #openstack-kolla00:13
*** crushil has joined #openstack-kolla00:13
*** crushil has quit IRC00:17
*** crushil has joined #openstack-kolla00:17
*** crushil has quit IRC00:20
*** crushil has joined #openstack-kolla00:20
*** crushil has quit IRC00:23
*** crushil has joined #openstack-kolla00:24
*** crushil has quit IRC00:27
*** crushil has joined #openstack-kolla00:27
*** crushil has quit IRC00:30
*** crushil has joined #openstack-kolla00:31
*** crushil has quit IRC00:34
*** crushil has joined #openstack-kolla00:34
*** crushil has quit IRC00:37
*** crushil has joined #openstack-kolla00:38
*** crushil has quit IRC00:41
*** crushil has joined #openstack-kolla00:41
*** schwicht has joined #openstack-kolla00:42
*** cu5 has quit IRC00:44
*** crushil has quit IRC00:44
*** cu5 has joined #openstack-kolla00:44
*** crushil has joined #openstack-kolla00:44
*** duonghq has joined #openstack-kolla00:50
duonghqmorning guys00:50
*** crushil has quit IRC00:51
openstackgerritpangliye proposed openstack/kolla-ansible master: update configuration of telegraf "config_files"  https://review.openstack.org/44688800:51
openstackgerritpangliye proposed openstack/kolla-ansible master: Update configuration of Telegraf retention_policy  https://review.openstack.org/44717900:53
sdakemorning duonghq00:53
duonghqhi sdake00:54
sdakeduonghq finally back in the office now - \o/00:54
*** tovin07_ has joined #openstack-kolla00:55
*** eaguilar has quit IRC00:57
*** schwicht has quit IRC00:58
duonghqsdake, glad to here that,00:58
*** qiliang27 has joined #openstack-kolla01:09
*** cuongnv has joined #openstack-kolla01:12
sdakeduonghq just read the logs from the droproot discussion01:19
sdakeduonghq it appeared like youwere going to ask me a question01:19
duonghqsdake, yup, I asked you one day later01:19
sdakecool01:19
sdakeso allset then?01:19
duonghqyes, after that, we decided to close the bug: drop root for crontab01:20
*** eaguilar has joined #openstack-kolla01:23
*** jrobinson_ has joined #openstack-kolla01:28
*** jrobinson_ has quit IRC01:29
*** jrobinson_ has joined #openstack-kolla01:30
*** jrobinson has quit IRC01:31
*** jrobinson_ is now known as jrobinson01:31
*** zhubingbing_ has joined #openstack-kolla01:31
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Update the "virt_driver" to "virt_type"  https://review.openstack.org/44733601:35
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Update the "virt_driver" to "virt_type"  https://review.openstack.org/44733601:36
sdakeduonghq https://review.openstack.org/#/c/411043/301:41
duonghqsdake, I will abandon it, seem that nobody care about this atm :)01:44
sdakecares about which01:44
sdakeuse cases?01:44
sdakeone problem we have is a lack of review capacity01:45
duonghqthe way which I proposed: use temporary review for use cases contribution01:45
sdakeduonghq if you want to do that - that works put a [DNM} in the front of the message header to keep in queue01:45
sdakethat tells reviewers that it is not ready for merge01:45
sdakean alternative approach is to set workflow -101:45
duonghqthe problem is: I'm not sure if anybody like that way to tracking use cases01:46
duonghqhow do you think?01:46
sdaketracking use cases is best done in blueprints01:48
duonghqyes01:48
zhubingbing_agree01:56
sdakezhubingbing_ how are you this fine evening01:58
* sdake got a fitbit tracker and has been averaging 7 hours of sleep a night01:59
sdakesurprising to me, as I thought I was averaging 6 :)01:59
zhubingbing_;)01:59
sdakezhubingbing_ i see your review related to fluentd was abandoned and unabandoned02:00
zhubingbing_yes02:00
sdakezhubingbing_ could you explain?02:00
sdakemisclick or planning to submit a new review?02:00
zhubingbing_Fluentd should be every pod should have,02:02
zhubingbing_i don't sure my patch is right02:03
zhubingbing_I need to look at the code again and think about it02:03
zhubingbing_;)02:03
zhubingbing_My English is so bad02:04
sdakeevery kubernetes deployment object should have a fluentd process, or every microchart?02:14
zhubingbing_yes02:15
sdakeyes to which - both? :)02:15
zhubingbing_every kubernetes deployment object should have a fluentd process02:15
zhubingbing_pod02:15
*** daidv has joined #openstack-kolla02:17
zhubingbing_https://github.com/openstack/kolla-kubernetes/blob/master/helm/kolla-common/templates/_common_lib.yaml02:17
zhubingbing_sdake02:17
zhubingbing_same as this02:17
sdakedo you mean this? https://github.com/openstack/kolla-kubernetes/blob/master/helm/kolla-common/templates/_common_lib.yaml#L3002:18
zhubingbing_yes02:19
sdakeanything that uses the common_containers macro?02:19
zhubingbing_kfox1111 tell me we should same as this to do02:20
sdakezhubingbing_ have a irc log handy?02:21
zhubingbing_i finding02:21
duonghqzhubingbing_, which is tag of your mariadb in k8s cluster?02:23
zhubingbing_http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2017-03-15.log.html#t2017-03-15T13:50:0002:25
zhubingbing_4.0.0 ?02:25
zhubingbing_sdake link http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2017-03-15.log.html#t2017-03-15T13:50:0002:25
duonghqhmm02:26
zhubingbing_duonghq i don't know tag what 's mean  ~~02:27
duonghqdocker images02:27
duonghqthe tag column02:27
zhubingbing_i know your problems02:27
zhubingbing_;) i don‘t running mariadb in k8s02:28
zhubingbing_you02:28
duonghqI use helm to deploy mariadb02:28
duonghqyou don't?02:28
zhubingbing_you don‘t running mariadb in k8s ,02:28
zhubingbing_i use helm02:28
zhubingbing_do you deploy success?02:28
duonghqno, mariadb stuck02:29
zhubingbing_i02:29
zhubingbing_i know your problems02:29
zhubingbing_-)02:29
duonghqya, still stuck02:30
duonghqthe k8s cluster deployed by kargo is very stable02:30
sdakethanks zhubingbing_02:30
zhubingbing_I can help you solve this problem duonghq02:31
duonghqthe log of bootstrap: http://paste.openstack.org/show/603355/02:31
zhubingbing_yes02:31
zhubingbing_i know this problem02:31
*** japestinho has joined #openstack-kolla02:32
zhubingbing_first you should remove /var/lib/kolla/volumes/mariadb02:33
zhubingbing_rm -rf /var/lib/kolla/volumes/mariadb/*02:34
zhubingbing_next  helm delete --purge mariadb02:34
zhubingbing_finally helm install again02:34
sdakezhubingbing_ a better workflow for that solution si to helm delete --purge mariadb and then rm -rf the volumes02:35
sdake(I think your workflow is out of order to start over)02:35
zhubingbing_yes02:35
zhubingbing_;)02:35
zhubingbing_sdake it is right02:35
zhubingbing_sdake say right02:36
duonghqsdake, zhubingbing_ thanks, I already did it last Friday, no luck, but today, it's fine02:36
duonghqdon't know why02:36
sdakeduonghq what have people been using to deploy kubernetes this last two weeks instead of halcyon which apparently has some problems?02:37
sdakeduonghq kargo or kubeadm?02:37
zhubingbing_it’s mariadb a bug02:37
duonghqsdake, I'm using kargo02:37
sdakedoes kargo do vms?02:37
sdakeduonghq or you setting up on bare metal?02:37
duonghqI created 3 vms (kvm),02:38
duonghqand point kargo to those02:38
duonghqkargo take the duty02:38
sdakekubeadm can do the same thing02:38
sdakedid you try out kubeadm?02:38
duonghqI tried it last year, I slapped me many time, this year I haven't02:39
zhubingbing_sdake i use kubeadm02:39
zhubingbing_;)02:39
zhubingbing_doughq it‘s mariadb bug,not k8s02:39
duonghqzhubingbing_, can you explain?02:39
zhubingbing_yeah02:40
sdakewe have been working on a workfow for deployment in production in https://etherpad.openstack.org/p/kolla-kubernetes-deploy-guide-BP02:40
duonghqsdake, I follow this workflow02:40
duonghqand stuck with mariadb02:40
sdakeduonghq nice02:40
sdakeduonghq i think we can maek the first part (whether to use kubeadm or kargo or bring your own kubernetes deployment tool) up to the operator02:41
sdakeduonghq how well does the workflow work for you?02:41
sdakeduonghq it sounds like "not well" :(02:41
zhubingbing_if mariadb has been created before, mariadb.sock file if not deleted, will retain the previous data.02:41
duonghqI got trouble with mariadb from kolla-ansible, so I think mariadb don't like me, if I can get over this, maybe everything will be fine02:41
zhubingbing_so mysql-safe will need you create new root password02:41
sdakeduonghq trouble with mariadb from kolla-ansible how?02:42
duonghqiirc, I got stuck with Galera, WSREP... it was a bug02:43
duonghqbut it's fine now02:43
duonghqzhubingbing_,  got it02:43
sdakeah - so mariadb was broken but is no longer02:43
sdakeduonghq so in theory those docs are good to convert to rst?02:43
duonghqso I'll add solving procedure to the guide02:43
sdakeas is the docs are hard to understand - i'd like to get them into rst as soon as possible02:43
zhubingbing_;)02:43
sdakeand I have all monday to do so02:43
sdakenobody followed the directions and added 'TESTED" with a date however02:44
sdakezhubingbing_ did those instructoins work for you?02:44
duonghqhmm, I think we can convert to rst, and add some progress later,02:45
sdakekargo has some wierd dns thing which may make things not work properly02:45
sdakekargo needs some workaround in the resolver workaround02:46
sdakewe got workarounds for ourworkarounds ;)02:46
duonghqso, I should move back to kubeadm or find workaround for kargo, seem tricky02:46
duonghqone more think, we use different tag (which mean different version) for different microservice?02:47
duonghq*thing02:47
zhubingbing_How to build k8s cluster, I think we can refer to K8s official website ;)02:48
duonghqzhubingbing_, can you give me link?02:49
zhubingbing_ok02:49
duonghqlast time I tried, no luck for me02:50
zhubingbing_https://kubernetes.io/docs/02:50
zhubingbing_kargo and kubedm02:50
duonghqokay02:51
duonghqso we should note that we recommend that way02:51
zhubingbing_i thinks sow02:52
zhubingbing_so02:52
duonghqnow, I got this error: Entrypoint WARNING: 2017/03/20 02:54:03 entrypoint.go:81: Resolving dependency for mariadb-init-element failed: Get https://10.233.0.1:443/apis/batch/v1/namespaces/kolla/jobs/mariadb-init-element: dial tcp 10.233.0.1:443: getsockopt: no route to host02:53
duonghq02:53
zhubingbing_i am learning how to note ;)02:53
zhubingbing_dns?02:54
duonghqyup, dns again02:54
zhubingbing_i suggest dns ip is setting the machine ip02:56
openstackgerritGao Zexu proposed openstack/kolla-ansible master: Add a missing blank space  https://review.openstack.org/44734802:58
duonghqzhubingbing_, you mean the configmap?03:08
*** Margin has joined #openstack-kolla03:10
zhubingbing_cloud.yaml03:14
sdakehey folks looks like the etherpad was edited on March 9th and critical data was delete03:19
sdaked03:19
*** dave-mccowan has quit IRC03:20
zhubingbing_roger03:21
sdakei'll get an rst pulled down from pre-9th and check the changes after the 9th for this same sort of behavior03:21
sdakeno wonder everyone is struggling to get the docs deployed03:22
*** zhurong has joined #openstack-kolla03:25
zhubingbing_sdake  when do we make a deployment command03:27
sdakezhubingbing_ you mean like kolla-kubernetes deploy?03:28
zhubingbing_same as kolla-ansible deploy03:28
zhubingbing_yes03:28
zhubingbing_yes03:28
sdakewe are building up the stack03:28
sdakethe next step of implementation is the external config maps03:28
zhubingbing_are we planning?03:30
zhubingbing_ok03:31
duonghqzhubingbing_, which section in cloud.yaml?03:34
sdakezhubingbing_ lets get a manual deploy working first ;)03:41
zhubingbing_sorry dough03:42
zhubingbing_i was not here03:42
zhubingbing_sdake,https://etherpad.openstack.org/p/kolla-kubernetes-deploy-guide-BP i thinks it is good03:42
zhubingbing_but we can optimize this file03:43
sdakezhubingbing_ there was a bit of vandalism - working on removing that03:47
sdakeand then its going in gerrit where it can't be vandalized03:48
zhubingbing_ok03:48
zhubingbing_so we should write a new deploy gudie03:49
zhubingbing_sdake https://review.openstack.org/#/c/439740/03:50
sdakezhubingbing_ that patch needs to be made to pass the gate03:50
sdakeit is correct, however it fails on the gate03:50
sdakezhubingbing_ if you want to do that instead of fluentd, that would have a larger immediate impact03:51
zhubingbing_this patch we should merge it ;)03:51
sdakeI've been traveling for 3 weeks03:51
*** eaguilar has quit IRC03:51
sdake2 weeks03:51
duonghqsdake, why we still use mariadb 2.0.2 in k8s?03:51
sdakeand the week before was very busy haven't had time to rework the gate for this particular patch03:51
zhubingbing_i help03:51
sdakeduonghq no clue03:51
zhubingbing_;)03:51
zhubingbing_duonghq i use 4.0.003:52
zhubingbing_;)03:52
sdakeduonghq from what I gather, kfox1111 seems to indicate it makes migration easier for existing deployments03:52
sdakealthough kolla-kubernetes in my mind will be a mostly greenfield deployment so the docs should indicate as much03:52
duonghqya,03:52
duonghqagreed with sdake03:52
duonghqzhubingbing_,  ok03:52
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Deployment Guide Documentation  https://review.openstack.org/44735603:52
*** Margin has quit IRC03:53
zhubingbing_duonghq  sdake we should finish Deployment Guide Documentation in this week03:59
zhubingbing_;)03:59
sdakezhubingbing_ YES03:59
duonghqyup04:00
*** jrobinson has quit IRC04:00
zhubingbing_ok04:00
*** jrobinson has joined #openstack-kolla04:05
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Deployment Guide Documentation  https://review.openstack.org/44735604:10
sdakehttps://review.openstack.org/#/c/447356/1..204:11
sdakeyou should see the changes between 1 and 2 - they are glorious04:11
sdakethe interim changes that is..04:12
duonghqya, got the mariadb up04:15
*** zhurong has quit IRC04:16
zhubingbing_;004:17
zhubingbing_;)04:17
zhubingbing_luncheon04:17
duonghqseem that we use many image from 2.0.004:17
zhubingbing_eating04:17
duonghq2.0.204:17
zhubingbing_;)04:17
duonghqany idea04:17
duonghqrabbitmq ....04:17
zhubingbing_default is 3.0.204:17
duonghqzhubingbing_, you need setting default to 3.0.2 manually or it's in code?04:18
zhubingbing_in code04:18
duonghqzhubingbing_, latest code is 2.0.204:20
duonghqI just try building cloud.yaml04:20
duonghqit put 2.0.2 in image_tag04:20
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Deployment Guide Documentation  https://review.openstack.org/44735604:21
sdakeyou can put 4.0.0 image tag in cloud.yaml04:22
sdakealthough I don't know that anyone has tested 4.0.0 - I'd go with 3.0.204:22
zhubingbing_https://github.com/openstack/kolla-kubernetes/blob/master/helm/all_values.yaml04:22
zhubingbing_i thinks 4.0.0 is better  3.0.204:22
zhubingbing_;)04:22
zhubingbing_yes04:25
duonghqsdake, zhubingbing_ should we discuss with Kevin to bump the default version to 3.0.2?04:26
sdakehe seems resistent04:26
sdakealthough we can put whatever we like in the deployment guide - and the answer there is 4.0.004:26
zhubingbing_2.0.2 is too old i think04:27
zhubingbing_yes04:27
sdakealthough lets get 3.0.2 deploy docs published - I know these instructions work and there is video evidence indicating as much :)04:27
duonghqalso, in https://etherpad.openstack.org/p/kolla-create-configmaps we miss many configmap *-logging04:27
sdakeduonghq no clue why that is04:27
duonghqsomething like this:   3m1m9{kubelet master}WarningFailedMountMountVolume.SetUp failed for volume "kubernetes.io/configmap/163e6fe6-0d25-11e7-a419-52540066ae24-logging-config" (spec.Name: "logging-config") pod "163e6fe6-0d25-11e7-a419-52540066ae24" (UID: "163e6fe6-0d25-11e7-a419-52540066ae24") with: configmaps "rabbitmq-logging" not found04:27
sdakeduonghq let me de-vandalize the deployment guide and I'll be right with you04:28
duonghqroger04:28
zhubingbing_duonghq04:29
duonghqzhubingbing_, here04:29
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Fix the remove mariadb volume failed  https://review.openstack.org/44735904:29
zhubingbing_you should kollakube res create configmap     mariadb keystone horizon rabbitmq memcached nova-api nova-conductor     nova-scheduler glance-api-haproxy glance-registry-haproxy glance-api     glance-registry neutron-server neutron-dhcp-agent neutron-l3-agent     neutron-metadata-agent neutron-openvswitch-agent openvswitch-db-server     openvswitch-vswitchd nova-libvirt nova-compute nova-consoleauth     nova-novncproxy nova-novncproxy-hapro04:29
zhubingbing_xy neutron-server-haproxy     nova-api-haproxy cinder-api cinder-api-haproxy cinder-backup     cinder-scheduler cinder-volume iscsid tgtd keepalived04:29
zhubingbing_http://paste.openstack.org/show/603360/04:30
duonghqzhubingbing_, already do this04:30
zhubingbing_you should create configmap before deploy04:30
duonghqbut rabbitmq-logging does not in the list04:30
duonghqzhubingbing_,  the rabbitmq statefulset is: http://paste.openstack.org/show/603361/04:31
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Deployment Guide Documentation  https://review.openstack.org/44735604:32
zhubingbing_[root@kube1 root]# aa get pods04:32
zhubingbing_NAME         READY     STATUS    RESTARTS   AGE04:32
zhubingbing_mariadb-0    1/1       Running   0          3d04:32
zhubingbing_rabbitmq-0   1/1       Running   0          1h04:32
zhubingbing_;)04:32
* duonghq get 2 helm service up and running 04:33
duonghqwith 2 more configmaps04:33
duonghqmariadb-logging and rabbitmq-logging04:33
zhubingbing_i know ;)04:33
*** daidv has quit IRC04:35
duonghqsituation becomes worst, it requires memcached-logging but none is defined04:39
sdakewonder where the logging stuff came from :)04:39
sdakethe etherpad for create-configmaps was not modified - although an unnamed author added a lowercase l on the 13th04:40
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Fix the remove mariadb volume failed  https://review.openstack.org/44735904:40
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Deployment Guide Documentation  https://review.openstack.org/44735604:40
sdakeduonghq https://review.openstack.org/#/c/447356/4..5/doc/source/deployment-guide.rst04:41
duonghqsdake, nice04:42
zhubingbing_nice04:43
duonghqhmm, zhubingbing_ where is logging section in cloud.yaml04:43
zhubingbing_i testing04:44
zhubingbing_wait04:44
zhubingbing_;)04:44
duonghqopenstack_logging_debug: "True"04:45
duonghqdoes it relate?04:45
zhubingbing_no04:45
zhubingbing_i don't about logging section04:46
zhubingbing_i have see the code04:46
zhubingbing_  - name: logging04:47
zhubingbing_          image: "duonghq:40000/kolla/centos-binary-fluentd:4.0.0"04:47
zhubingbing_          imagePullPolicy: "IfNotPresent"04:47
zhubingbing_          volumeMounts:04:47
zhubingbing_            - mountPath: /var/lib/kolla/config_files04:47
zhubingbing_              name: logging-config04:47
zhubingbing_            - mountPath: /var/log/kolla/04:47
zhubingbing_              name: kolla-logs04:47
zhubingbing_            - mountPath: /etc/localtime04:47
zhubingbing_              name: host-etc-localtime04:47
zhubingbing_              readOnly: true04:47
zhubingbing_          env:04:47
zhubingbing_            - name: KOLLA_CONFIG_STRATEGY04:47
zhubingbing_              value: COPY_ONCE04:47
zhubingbing_      volumes:04:47
zhubingbing_        - name: host-etc-localtime04:47
zhubingbing_          hostPath:04:47
zhubingbing_            path: /etc/localtime04:47
zhubingbing_        - name: kolla-logs04:47
zhubingbing_          emptyDir: {}04:47
zhubingbing_        - name: logging-config04:47
zhubingbing_          configMap:04:47
zhubingbing_            name: rabbitmq-logging04:47
zhubingbing_        - name: pod-main-config04:48
zhubingbing_          emptyDir: {}04:48
zhubingbing_        - name: rabbitmq-config04:48
zhubingbing_          configMap:04:48
zhubingbing_            name: rabbitmq04:48
zhubingbing_        - name: rabbitmq-persistent-storage04:48
zhubingbing_          persistentVolumeClaim:04:48
zhubingbing_            claimName: rabbitmq04:48
zhubingbing_sorry04:48
zhubingbing_;)04:48
zhubingbing_http://paste.openstack.org/show/603363/04:48
zhubingbing_https://github.com/openstack/kolla-kubernetes/blob/master/helm/kolla-common/templates/_common_lib.yaml#L3004:48
duonghqcan I disable it, due to something trigger configmap dependency to *-logging configmap04:50
*** rwsu has joined #openstack-kolla04:51
zhubingbing_I think there should be a switch04:51
zhubingbing_;)04:51
duonghqyup04:52
*** unicell1 has joined #openstack-kolla04:53
*** unicell has quit IRC04:54
zhubingbing_doughq i don‘t see about  logging config04:58
sdakezhubingbing_ --:(04:58
sdakeduonghq arey ou using cloud.yaml?04:58
*** zhurong has joined #openstack-kolla04:59
zhubingbing_;04:59
zhubingbing_https://github.com/openstack/kolla-kubernetes/blob/master/helm/kolla-common/templates/_common_lib.yaml#L2904:59
zhubingbing_this04:59
duonghqsdake, yes04:59
duonghqzhubingbing_, will test04:59
sdakeduonghq which etherpad did you us efor the reference04:59
zhubingbing_https://github.com/openstack/kolla-kubernetes/blob/master/helm/kolla-common/templates/_common_lib.yaml#L6105:00
duonghqsdake, your bp05:00
duonghqone was converted to review05:00
zhubingbing_http://paste.openstack.org/show/603364/05:02
zhubingbing_duonghq you can look my05:02
zhubingbing_my testing05:02
*** saneax-_-|AFK is now known as saneax05:07
sdakezhubingbing_ is it accurate to say you ahve a complete deployment operational with those instructions?05:07
sdakezhubingbing_ and also accurate to say duonghq does not05:07
sdakeand the delta is related to the logging?05:07
*** saneax is now known as saneax-_-|AFK05:08
zhubingbing_I'm not sure  where is logging on the switch05:08
zhubingbing_and i don‘t find logging configmap05:09
duonghqhmm, ok05:10
sdakezhubingbing_ do you ahve an operational AIO/05:10
duonghqI'll find that one05:10
zhubingbing_yes05:10
sdakezhubingbing_ can you paste your globals.yaml?05:10
zhubingbing_i deploy05:10
zhubingbing_ok05:10
sdakeduonghq can you compare your globals.yaml with zhubingbing_ 's?05:11
duonghqzhubingbing_, can you post your globals.yaml05:12
zhubingbing_wait05:12
zhubingbing_http://paste.openstack.org/show/603366/05:13
sdakezhubingbing_ how did you come up with that globals.yaml?05:14
zhubingbing_it's my globals.yaml05:14
*** zhurong has quit IRC05:14
duonghqmin, I need go out for awhile05:14
zhubingbing_ok05:15
duonghqWill try your global.conf05:15
duonghqthanks05:15
zhubingbing_http://paste.openstack.org/show/603367/05:16
zhubingbing_http://paste.openstack.org/show/603368/05:17
zhubingbing_my cloud.yaml05:17
duonghqzhubingbing_, no haproxy?05:18
sdakezhubingbing_ how did you generate cloud.yaml?05:18
zhubingbing_no haproxy05:18
*** skramaja has joined #openstack-kolla05:19
duonghqsorry guys, I need taking rest for a few mins,05:19
sdakeme too05:19
duonghqget back to you later05:19
sdakeenjoy :)05:19
sdakeits about 10pm here05:19
zhubingbing_in your bp05:19
zhubingbing_;)05:19
zhubingbing_kube_logger: false05:19
zhubingbing_i think should set it05:20
*** saneax-_-|AFK is now known as saneax05:20
zhubingbing_;) i continue test log05:20
zhubingbing_;)05:20
sdakeduonghq rwellum updated the etherpad on the 13th with which appears to be a more correct cloud.yaml file05:21
sdakeor a less correct cloud.yaml05:21
sdakenot sure which :)05:21
duonghqsdake, hmm, ok05:22
sdakeit includes the following snippet:05:22
sdake(forgive spam):     mariadb:05:22
sdake      all:05:22
sdake        database_user: root05:22
sdake        image_tag: 3.0.305:22
sdake        node_port: 330605:22
sdake        node_port_enabled: false05:22
sdake        port: 330605:22
sdake        port_external: false05:22
sdake        kube_logger: false05:22
sdakethe version I posted lacked a kube_logger: false setting for mariadb05:23
sdakeit is possible that from march 1st to march 13th there was some regression in the code base which caused kube_logger to break05:23
sdake(for mariadb)05:23
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Delete the deprecated option from the group "DEFAULT"  https://review.openstack.org/44736805:23
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Delete the deprecated option from the group "DEFAULT"  https://review.openstack.org/44736805:25
duonghqsdake, I got it error both for mariadb, rabbitmq, memcached05:26
duonghqWill see what kube_logger has done for my installation05:27
duonghqcya05:27
sdakeduonghq when you return - try changing helm/all_values.yaml kube_logger:false05:29
sdakeduonghq you will need to go through the prebuild process again05:30
zhubingbing_yes05:33
zhubingbing_duonghq are you ok ?05:37
*** Margin has joined #openstack-kolla05:52
*** caowei has joined #openstack-kolla05:58
*** jaosorior has joined #openstack-kolla06:04
duonghqzhubingbing_, sdake seem that it's ok06:22
duonghqthanks06:22
zhubingbing_yeah06:22
zhubingbing_i reading about kube_logger06:23
zhubingbing_ code06:23
duonghqyup, it's kube_logger, not sure why it's here before your fluentd06:24
zhubingbing_i thinks it's have some problems  about  kube_logger06:25
zhubingbing_i have testing06:25
jaosoriorare kolla images uploaded somewhere to dockerhub? is it possible for me to just do docker run with a specific image and just try out a service?06:27
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Fix Telegraf startup config files issue  https://review.openstack.org/44738206:29
zhubingbing_duonghq  do you know {{- include .extraConfigmapConfig . | indent 12 }}06:30
zhubingbing_what's mean with "indent 12"06:30
duonghqit include the config map, and push 12 spaces before each line of code06:35
duonghqzhubingbing_,06:35
duonghqjaosorior, no06:35
zhubingbing_ok06:36
*** masuberu has joined #openstack-kolla06:37
duonghqzhubingbing_, can you can post-deploy with your global.yaml06:42
jaosoriorduonghq: thanks. I'll proceed to build images then.06:42
zhubingbing_hmm yes06:42
duonghqzhubingbing_, only http://paste.openstack.org/show/603366/ ?06:44
*** schwicht has joined #openstack-kolla06:46
zhubingbing_http://paste.openstack.org/show/603367/06:48
zhubingbing_duonghq06:48
duonghqokay06:51
duonghqseem that we donot have teardown job jet06:51
duonghqyet06:51
*** masuberu has quit IRC06:52
zhubingbing_yes06:52
*** jaosorior has quit IRC06:53
*** jaosorior has joined #openstack-kolla06:55
*** jrobinson has quit IRC07:00
zhubingbing_duonghq07:08
zhubingbing_[root@kube1 ~]# aa get pods07:08
zhubingbing_NAME         READY     STATUS    RESTARTS   AGE07:08
zhubingbing_mariadb-0    1/1       Running   0          3d07:08
zhubingbing_rabbitmq-0   2/2       Running   0          1m07:08
zhubingbing_[root@kube1 ~]# docker ps | grep flu07:08
zhubingbing_0bd5f9fbc80b        192.168.121.64:4000/kolla/centos-source-fluentd:4.0.0           "kolla_start"            About a minute ago   Up About a minute                       k8s_logging.8446b10c_rabbitmq-0_kolla_ac0f5db2-0d3b-11e7-b389-525400b7c6af_864ad21307:08
zhubingbing_;)07:08
zhubingbing_I know how to  play logging in kolla-k8s07:09
duonghqhmm, do you need fluentd?07:12
duonghqah, understand07:12
duonghqyou get log directory from the logging container07:12
duonghq*directly07:12
zhubingbing_yes07:13
zhubingbing_But I think this design seems a bit of a problem07:14
zhubingbing_;)07:14
*** jaosorior has quit IRC07:14
*** jaosorior has joined #openstack-kolla07:15
*** jaosorior has quit IRC07:16
*** masuberu has joined #openstack-kolla07:18
*** jaosorior has joined #openstack-kolla07:19
*** satyar has joined #openstack-kolla07:20
duonghqzhubingbing_, can you provide some more detail07:23
duonghqabout problem of design?07:23
zhubingbing_wait a few min07:23
satyarHi zhubingbing_07:24
satyarhi Jeffrey4l__07:24
Jeffrey4l__sup satyar07:28
satyarHow are you Jeffrey4l__07:28
Jeffrey4l__not bad except busying ;)07:28
satyarha ha ha07:29
satyarwant to check if you have tried freezer07:29
satyaropenstack freezer ;)07:29
*** Margin has quit IRC07:30
*** Margin has joined #openstack-kolla07:30
*** Jeffrey4l__ has quit IRC07:33
*** zhubingbing_ has quit IRC07:33
*** zhubingbing_ has joined #openstack-kolla07:34
*** MarginHu has joined #openstack-kolla07:34
*** Margin has quit IRC07:35
*** manheim has joined #openstack-kolla07:35
*** Jeffrey4l__ has joined #openstack-kolla07:36
*** Jezekus has joined #openstack-kolla07:38
*** MarginHu has quit IRC07:43
*** maniram477 has joined #openstack-kolla07:44
*** zhugaoxiao has quit IRC07:57
*** zhugaoxiao has joined #openstack-kolla07:58
*** matrohon has joined #openstack-kolla08:00
*** shardy has joined #openstack-kolla08:04
*** shardy has joined #openstack-kolla08:07
*** maniram477 has quit IRC08:09
*** pcaruana has joined #openstack-kolla08:14
*** Serlex has joined #openstack-kolla08:15
*** Masber_080 has joined #openstack-kolla08:28
*** masuberu has quit IRC08:29
*** matrohon has quit IRC08:32
*** mpansky has joined #openstack-kolla08:36
*** mnasiadka has joined #openstack-kolla08:38
*** hrw has quit IRC08:38
*** egonzalez has joined #openstack-kolla08:40
*** rmart04 has joined #openstack-kolla08:54
*** athomas has joined #openstack-kolla08:57
hawihi. i have question regarding error "Error: Unable to get quota info." after installation. is it possible to fix it somehow or what is actually missing?08:59
hawisome API endpoint is wrong?08:59
egonzalezhawi, which quota?09:00
*** mpansky has quit IRC09:00
*** mpansky has joined #openstack-kolla09:00
hawii'm getting it from Horizon UI -> Admin -> System -> Defaults09:00
*** duke__ has joined #openstack-kolla09:01
*** openstackgerrit has quit IRC09:02
egonzalezhawi, what version are you using?09:02
*** hrw has joined #openstack-kolla09:04
*** schwicht has joined #openstack-kolla09:07
*** mpansky has quit IRC09:07
*** mpansky has joined #openstack-kolla09:08
hawiocata on ubuntu 16.04.2. i have no idea how to check kolla/kolla-ansible version, but when downloaded, i took stable/ocata branches09:08
*** schwicht has quit IRC09:11
*** Masber_080 has quit IRC09:12
egonzalezhawi, can you check if quotas are working? to see if the issue is with horizon or general to quotas09:12
egonzalezfrom CLI ^^ openstack quota show09:13
hawiProject ID 5973eefd76fb4227b3a44273208fee4d is not a valid project. (HTTP 400) (Request-ID: req-92044052-5732-4872-b637-9c4f064e2ee8)09:16
hawifor admin tenant09:16
egonzalezhawi, i suspect you are using master instead of ocata https://bugs.launchpad.net/kolla-ansible/+bug/166866309:18
openstackLaunchpad bug 1668663 in kolla-ansible "nova quota update command error" [Undecided,In progress] - Assigned to Eduardo Gonzalez (egonzalez90)09:18
egonzalezthis bug only affect to master(pike)09:19
*** mpansky has quit IRC09:24
hawiin somehow i was able to install it without any errors...i'll check it, what i actually have09:24
*** mpansky has joined #openstack-kolla09:25
hawithanks09:25
*** masuberu has joined #openstack-kolla09:28
hawiegonzalez: i think i need to reinstall everything09:37
thomas_oneillmorning all09:40
egonzalezhawi, if using ocata, better install kolla-ansible with pip install kolla-ansible==4.0.009:41
thomas_oneillI'm trying to fix up the bifrost-base image with it's mysql-server/mariadb-server hack, there is this in bifrost https://github.com/openstack/bifrost/tree/master/playbooks/roles/bifrost-ironic-install/defaults09:41
egonzalezhawi, this way ensure are using correct version,  unless you need to use development branch09:41
thomas_oneillwhen I use the kolla-build.conf with the type = local and the location pointing to the location of the git repo on the machine I'm working on, it doesn't work09:41
thomas_oneilllike I change all these defaults to mariadb-server instead of mysql-server in the bifrost repo on my local machine, I set up the kolla-build.conf to point at this local path with this repo with the changes, and then I run the image and go into the container with bash and the bifrost that's in there is the same old bifrost with the usual stuff from the 3.0.1 tarball and not my changes09:42
thomas_oneillis there an easier way to debug this without just debugging the actual image/build.py line by line lol or does anybody have any suggestions09:43
*** blallau has joined #openstack-kolla09:44
*** masuberu has quit IRC09:44
*** duonghq has quit IRC09:53
*** mgoddard has joined #openstack-kolla09:53
*** athomas has quit IRC10:02
*** cuongnv has quit IRC10:04
*** pbourke has quit IRC10:07
*** pbourke has joined #openstack-kolla10:07
*** jmccarthy has joined #openstack-kolla10:09
*** athomas has joined #openstack-kolla10:09
*** manheim has quit IRC10:10
*** tovin07_ has quit IRC10:16
thomas_oneillalso could this be workflowed if nobody has any issues: https://review.openstack.org/#/c/443747/10:29
*** satyar has quit IRC10:30
thomas_oneillegonzalez: Jeffrey4l__ zhubingbing_ ^^ sorry this has been hanging for many days nowe10:31
Daviey_Hi, please could i get a second review on https://review.openstack.org/#/c/444771/ .. it has been sad idle for a bit, and pretty urgent10:34
Daviey_thomas_oneill: How confident are you the "when" stanza is correct? https://review.openstack.org/#/c/443747/7/ansible/roles/neutron/handlers/main.yml10:35
thomas_oneillDaviey_: 56% confident. Why?10:36
Daviey_hah10:38
Daviey_Jus curious... it jumped out at me as something to check10:38
Daviey_thomas_oneill: Also, where is neutron_bgp_router_id defined?10:38
thomas_oneillgroup_vars10:38
Daviey_thomas_oneill: oh yes, missed that. Thanks10:39
thomas_oneillI did look at your change too, I have no understanding/experience of heka though, so cannot give review :p10:43
Daviey_thomas_oneill: +W'd10:43
thomas_oneilloh ty :)10:43
*** openstackgerrit has joined #openstack-kolla10:47
openstackgerritMerged openstack/kolla-ansible master: Add neutron-bgp-dragent playbooks and sensible defaults.  https://review.openstack.org/44374710:47
*** masuberu has joined #openstack-kolla10:48
*** mpansky has quit IRC10:52
*** matrohon has joined #openstack-kolla10:54
hawiegonzalez: still the same issue10:57
hawiused pip install to have 4.0.0 version for kolla-ansible and reinstalled everything10:57
egonzalezhawi, images were rebuilt ?10:58
*** masuberu has quit IRC11:00
hawiegonzalez: you mean, also kolla-build to build new images in registry?11:00
egonzalezhawi, yep, the issue is in nova codebase, if the images used are master the bug still present11:01
hawiok, will rebuild them also completely. i'm pretty sure that i used not master kolla to build them, but i'll rebuild them as well.11:03
*** schwicht has joined #openstack-kolla11:04
hawiegonzalez: how to ensure i'm building them for 4.0.0?11:04
egonzalezpip install kolla==4.0.011:05
hawiand the  kolla-build -t source -b ubuntu --registry ip:port --push ?11:09
*** mpansky has joined #openstack-kolla11:10
*** rwallner has joined #openstack-kolla11:10
*** manheim has joined #openstack-kolla11:11
egonzalezhawi, yep11:12
*** matrohon has quit IRC11:12
egonzalezhawi, docker images are in docker hub, don't need to rebuild them, just push from there11:14
*** rwellum has joined #openstack-kolla11:15
*** zhurong has joined #openstack-kolla11:17
*** matrohon has joined #openstack-kolla11:18
hawiegonzalez: i had knowledge that for multinode i need to have my own registry.11:23
egonzalezhawi, if use public docker registry don't need your own11:24
*** masuberu has joined #openstack-kolla11:26
*** mnasiadka has quit IRC11:32
*** Jeffrey4l_ has joined #openstack-kolla11:34
*** Jeffrey4l__ has quit IRC11:36
*** zhurong has quit IRC11:37
openstackgerritYu Chaochao proposed openstack/kolla master: Remove py34 settings from gating  https://review.openstack.org/44724711:56
*** manheim has quit IRC11:59
*** manheim has joined #openstack-kolla11:59
sdakemorning folks12:03
*** schwicht has quit IRC12:06
spsuryamorning sdake12:08
*** dave-mccowan has joined #openstack-kolla12:08
*** nea1 has quit IRC12:09
*** masuberu has quit IRC12:11
*** rhallisey has joined #openstack-kolla12:11
jaosoriormandre: any idea why those two are both trying to bind to 443? are those tests running with SSL?12:13
*** mnasiadka has joined #openstack-kolla12:14
jaosoriormandre: or, how can we reproduce gate-kolla-dsvm-deploy-centos-binary-centos-7-nv to log into the containers and see why something is trying to use SSL there :/ I can see why dashboard would be trying, but not why nova-placement API.12:14
*** Jezekus has quit IRC12:19
*** schwicht has joined #openstack-kolla12:25
hawiegonzalez: thanks, everything is fine now!12:27
*** matrohon has quit IRC12:28
*** schwicht has quit IRC12:30
*** matrohon has joined #openstack-kolla12:31
mnasiadkaIs it only me, or horizon in ubuntu/binary build (stable/ocata) is missing proper path to images?12:35
*** schwicht has joined #openstack-kolla12:36
*** schwicht has quit IRC12:37
openstackgerritYu Chaochao proposed openstack/kolla master: Remove py34 settings from gating  https://review.openstack.org/44724712:38
*** schwicht_at_work has joined #openstack-kolla12:38
mnasiadkaYeah, it does12:42
*** shardy is now known as shardy_lunch12:44
mnasermorning everyone12:48
spsuryamorning mnaser12:48
spsuryainc0:  hi...12:49
spsuryait would be great if yo review this   https://review.openstack.org/#/c/425446/12:50
mandrejaosorior: I haven't looked into it why it tries to bind to port 443 yet12:50
spsuryaas gate is green now12:50
mandrejaosorior: the CI job simply does a tools/deploy_aio.sh from kolla-ansible with the centos binary image it just built12:50
hawii have generic question regarding Kolla. What should i do, when i change globals, in order to apply changes? is it kolla-ansible reconfigure or just deploy again, i guess upgrade is more for replacing images with newer ones?12:52
*** schwicht_at_work has quit IRC12:52
mnaserhawi i think reconfigure => deploy in later verisons of kolla-ansible12:53
*** satyar has joined #openstack-kolla12:54
*** nea1 has joined #openstack-kolla12:56
*** srwilkers has joined #openstack-kolla12:59
*** zhubingbing_ has quit IRC12:59
*** mpansky has quit IRC13:00
pbourkeJeffrey4l_: egonzalez: sdake: can one or more of you please revisit https://review.openstack.org/#/c/400187/13:00
pbourkeit's badly needed13:00
*** mpansky has joined #openstack-kolla13:00
pbourkereasons it makes sense are outlined in comments13:01
Jeffrey4l_pbourke, i change my thought. use multi glance cause almost the same issue. i think vip is more better. and operators should sync ( or use share storage )13:03
hawimnaser: so, if i add enable_neutron_lbaas: "yes", then i need to do kolla-ansible -i inventory deploy, yes?13:04
sdakepbourke changed my vote - apologies for not getting back to that review13:04
*** lamt has joined #openstack-kolla13:04
mnaserthat should do the job hawi13:04
mnasergranted i never tested it personally13:04
sdakepbourke i have a hard time actively keeping up with the amount of email i have passing through my inbox, and review email is tough to process13:05
hawimnaser: i started with reconfigure right now (it sounded more like), but if it fails, then i'll go with deploy :)13:05
sdakepbourke feel free to ping if you need a specific review - thanks :)13:05
openstackgerritMerged openstack/kolla-ansible master: Use kolla_internal_vip_address for glance_api servers  https://review.openstack.org/40018713:06
hawimnaser: reconfigure did the job13:07
*** lamt has quit IRC13:08
sdakeJeffrey4l_ i saw in wednesday's meeting notes, there is activity underway to get images built in infra13:09
sdakeJeffrey4l_ i spent over 1 year working on that particular problem with little to no success13:09
sdakeJeffrey4l_ curious if you know the current status of that solution?13:10
Jeffrey4l_no solution right now.13:10
sdakemnaser had mentioned he could talk to infra about how to make it so13:11
Jeffrey4l_still need find a way to save hub.docker.c credential.13:11
sdakein the meantime, I'd suggest an automated workaround based upon portdirect 's repo and a volunteer effort13:11
mnasersdake let me share a discussion i had with fungi from infra13:11
sdakeJeffrey4l_ yup the credentials and the build times are the two things that stopped my progress13:11
sdakemnaser thanks :)13:11
Jeffrey4l_yep. i saw their talks.13:11
*** goldyfruit has joined #openstack-kolla13:11
sdakemnaser apparently I was asleep :)13:11
mnasersdake Jeffrey4l_  http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-03-18.log.html#t2017-03-18T13:29:0413:12
*** lamt has joined #openstack-kolla13:12
Jeffrey4l_seems we need set up another slave progress, right?13:12
mnaserso we'd need a dedicated slave where credentials are store under root and the "job" file, ex: push image process happens under another user13:12
Jeffrey4l_then which part is impossible now? like pypi case?13:13
mnaserso no one can craft a change which will let that password change13:13
mnaseroh i dont think its impossible, my suggestion was to have a push_images.sh which does the push after things are built13:13
mnaserand sudo access is locked down to that only13:14
Jeffrey4l_before pushing the image, should download it from tarballs.o.o site? or build the image agains?13:14
sdakemnaser: for low-volume/low-data jobs which can run without root access and entirely from statically-defined scripts and preinstalled applications, yes we have some persistent slaves which can act as credential safes13:14
sdakecredential safes13:15
mnaseryeah well we'd have a dedicated slave13:15
mnaserfor docker stuff13:15
mnaserbecause of the volume and data involved13:15
sdakerockin13:15
sdakewould the dedicated slave build the image - or pull it from tarballs.oo?13:15
sdakeimage/images13:16
mnaserthe idea was: dedicated slave build image under "jenkins" user, sudo /usr/local/bin/push_images $TAG and that pushes it13:16
mnaseri mean the choice is up to us but i think its probably better to let it build it13:16
*** lamt has quit IRC13:16
mnaserrather than downloading 2.5gb and pushing it out again13:16
Jeffrey4l_is it possible to add jenkins user to docker group?13:17
mnaserJeffrey4l_ the idea is that this is a persistent slave that never gets deleted13:17
sdakethe problem with that is that rebuilding does not actually always result in the same thing the gate tested13:17
mnaserso we configure it the way we want13:17
mnasersdake thats a good point13:17
sdakemnaser a curl - untar - tar and push13:17
mnaseror we get a hosted registry backed by swift13:17
sdakethat would be very easy to vet - much easier than infra going trough kolla-build.py :)13:17
sdakemnaser i'd like to keep things simple :)13:18
mnaserideally we'd also ask for the slave to be hosted in the same region as tarballs.o.13:18
sdakeright13:18
Jeffrey4l_that will be great.13:18
sdakethen the question becomes, how to release per tag?13:19
mnaserthere is a release pipeline in zuul13:19
sdakespin in a script on a git clone to checkout the repo?13:19
mnaserwhich gets triggered when you tag13:19
sdakei know that13:19
sdakehow does that interact with persistent slaves?13:19
mnaserid assume the persistent slave gets a job with all the ZUUL_* stuff13:20
Jeffrey4l_current logical should works when we add the job into release pipeline.13:20
*** lamt has joined #openstack-kolla13:20
mnaserand we check if there is ZUUL_TAG and tag with it13:20
mnaserif not, we tag ZUUL_BRANCH13:20
sdakethe persistent slave is always running - not run per job if I understand correctly13:20
mnaseryep, that's corret13:20
sdakeis the idea tha tthe release pineline would ssh into the release slave?13:20
mnaseri think with some zuul magic they can say "always run this job on this slave"13:21
mnaserso the release pipeline job + gate/merge job always hits the same "uploading" slave13:21
openstackgerritOpenStack Proposal Bot proposed openstack/kolla master: Updated from global requirements  https://review.openstack.org/44677113:21
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-ansible master: Updated from global requirements  https://review.openstack.org/44677213:21
Jeffrey4l_release slave should be configured run at the end of the jobs.13:21
*** m1dev has joined #openstack-kolla13:22
sdakei think we need more information on the magic - to prepare a script for infra to review13:22
sdakealso the persistent slaves need docker installed ;)13:22
mnaseryeah, im pretty sure they would get customized using system-config13:22
Jeffrey4l_for this point, technically, is it possible to push a docker registry without docker engine?13:22
*** eaguilar has joined #openstack-kolla13:23
mnasernope dont think so Jeffrey4l_13:23
sdakeit would be possible if you spent months writing a custom docker engine13:23
Jeffrey4l_lol13:23
sdakeso technically possible13:23
sdakefeasible - not really :)13:23
*** eaguilar has quit IRC13:24
mnaseronce people in the west coast start waking up today13:24
Jeffrey4l_just a few docker registry api. not related docker engine, actually.13:24
mnaserill try to poke some people if we can get ourself an initial machine13:24
*** jtriley has joined #openstack-kolla13:24
mnaserthen we can start the process of getting docker installed on it with puppet using system-config, and writing out a very simple script to push whats in the registry13:25
Jeffrey4l_mnaser, do u have any idea how to test  the release pipeline?13:25
mnaseroh also zuulv3 apparently has in-repo secrets13:25
*** lamt has quit IRC13:25
mnaserso that would be a nice thing to have13:25
Jeffrey4l_the issue is: when zuulv3 will be landed?13:25
mnasergood question13:25
mnaser /shrug13:25
mnaserJeffrey4l_ is that necessary? i mean whatever is tagged should already have passed tests13:25
mnaserin other cool news we migrated our nova, neutron, cinder and glance control plane to kolla over the weekend13:26
mnaserso woo13:26
Jeffrey4l_just wanna to make sure it works. and we need push tags registry tarballs to tarballs.o.o site.13:26
Jeffrey4l_that's cool13:26
Jeffrey4l_need add build/push image jobs into release pipeline.13:27
portdirectmornin' o/13:27
Jeffrey4l_morning13:28
*** shardy_lunch is now known as shardy13:28
Jeffrey4l_hrm. checked the code. simple add the build/push images job into release pipeline should work.13:30
hawiquestion regarding neutron: i would like to add provider networks to ml2_conf.ini, for vlan and flat. what is the best place to put it? i have ceph.conf in /etc/kolla/config, should i put ml2_conf.ini there as well?13:33
sdakemnaser nice!13:34
sdakeok - re zuul v313:34
sdakemy current speculation not based upon any factual data is as follows13:34
*** erhudy has joined #openstack-kolla13:34
sdakemordred had indicated in his last communication to the mailing list that he will provide more updates in the "next few months"13:34
sdakeor something to that effect13:35
sdakeJeffrey4l_ the earliest I htink we can expect zuul v3 is June based upon the word few (3 or more) in that statement13:35
Jeffrey4l_roger.13:36
openstackgerritAlicja Kwasniewska proposed openstack/kolla master: Added snap-telemetry container  https://review.openstack.org/44616413:36
sdakeJeffrey4l_ in speaking with the zuulv3 team, they have not disclosed their release timelines at all13:37
sdakeJeffrey4l_ I htink they dont want to commit and then miss - which is reasonable13:37
sdakewe struggle ever ycycle to release on time :)13:38
sdakemnaser re your migration - how did you go about it?13:39
sdakemnaser a brownfield migration doc would be fantastic13:39
sdakemnaser atleast some tribal knowledge on how it was done would also be useful13:39
mnasersdake: start up mariadb using kolla, start up rabbitmq using kolla, switch all data plan and old control plane to new rabbitmq, create db in new mariadb, migrate db, restart control plane services with db hosted on kolla, match configuration from old infra with kolla, deploy $service, now we have 2 control planes that are identical, test new control plane (we had the luxury of haproxy running before), when all is a-ok, turn off old control13:40
mnaser plane13:40
sdakemnaser note - I dont know how to write puppet code - nor do many people on the team13:40
mnasersdake thats okay, i can help doing this.  our infra ran extensively on puppet for quite sometime13:41
egonzalezhi guys, any idea about libvirtError: Activation of org.freedesktop.machine1 timed out13:41
egonzalez while creating instances13:41
nea1Hi, where do I find the logs of the services?13:42
egonzalezit was working before13:42
*** zhubingbing_ has joined #openstack-kolla13:42
sdakeegonzalez groan - never seen that one13:42
sdakeegonzalez that would imply a communication error to systemd13:42
sdakeegonzalez was libvirt possibly updated?13:42
sdakeegonzalez note dbus is used to communicate to systemd from libvirt13:43
sdakeegonzalez those are some components to look at - on your host or in the container13:43
egonzalezsdake, nope, no change13:43
sdakeegonzalez probably something changed :)13:43
sdakeegonzalez did you update your host at all?13:44
sdakemnaser your running mariadb in containers then?13:44
mnasersdake yeah, its running as part of it all now13:45
mnaseras part of the kolla deployment13:45
egonzalezsdake, nope is in the same state as when was deployed13:45
sdakemnaser running haproxy?13:45
mnasersdake yeah, we're still relying on our old haproxy (we used to run keepalived+haproxy) but we're soon going to switch to the kolla haproxy13:46
egonzalezsdake, dbus and machine8 services are in error state, but those services are static and activated from libivrt calls IIRC13:46
mnaserboth are running at once13:46
sdakemnaser i mean is enable_haproxy: yes set?13:46
mnaseryep13:46
sdakenice that is almost a full migration13:46
sdakealso the data plane?13:46
pbourkethanks for that sdake & Jeffrey4l_ :)13:47
sdakenote in this instance i mean things like neutron13:47
mnasersdake data plane is a wip, our next thing to tackle is migrating neutron control plane13:49
mnaserwe purposefully kept the same host names so that we can shutdown the service on $old_controller_n and start it up on $new_controller_n13:49
mnaserand we dont have to move ports around, it'll just detect itself13:49
sdakeegonzalez where are the logs stored now a adays for kolla-ansible for nea1 ?13:49
*** rhallisey has quit IRC13:50
egonzalez/var/lib/docker/volumes/kolla_logs as always ;)13:51
zhubingbing_hey guys13:52
*** crushil has joined #openstack-kolla13:52
zhubingbing_;)13:53
mnasero/13:53
sdakesup zhubingbing_13:53
zhubingbing_sup sdake13:53
sdakezhubingbing_ any progress on the deployment gerrit doc?13:53
sdakezhubingbing_ i crashed last night13:53
zhubingbing_i look it13:53
zhubingbing_;)13:54
sdakezhubingbing_ is it your end of day or beginning13:54
sdakeI think its your end - although hard to tell :)13:54
zhubingbing_i will beaginng to write13:54
*** lamt has joined #openstack-kolla13:54
sdakehttps://review.openstack.org/#/c/447356/13:55
zhubingbing_https://review.openstack.org/#/c/447356/13:55
sdakeyup :)13:55
zhubingbing_i look it ;)13:55
sdakeyes please review13:55
sdakeeveyrone that contributed to the etherpad - please review - lets remove all the extra crap13:55
zhubingbing_ok13:55
sdakeqwang are you about?13:55
sdakerwellum are you about?13:56
*** rhallisey has joined #openstack-kolla13:57
zhubingbing_sdake can i modify this patch ?13:57
sdakerwellum I determined why you were struggling so much with the deployment - the etherpad was vandalized interrupting eveyrone's work: https://review.openstack.org/#/c/447356/1..213:57
openstackgerritJeffrey Zhang proposed openstack/kolla master: Get correct tag name when job is running in release pipeline  https://review.openstack.org/44750713:58
nea1sdake: egonzalez thanks13:58
sdakezhubingbing_ I think a better way of doing the work is to review it although if you need to include big chunks or want to convert to rst, that wfm13:58
*** lamt has quit IRC13:58
zhubingbing_sure13:58
zhubingbing_rouger13:58
zhubingbing_roger13:58
sdakezhubingbing_ what did you want to do exactly13:58
sdakezhubingbing_ I am planning to spend the day on working on this doc - need some reviews from the ocntribs13:59
sdakezhubingbing_ how did you want to modify it?13:59
*** japestinho has quit IRC14:00
nea1how do I at best see if the node is done with the reboot and all services are up14:00
zhubingbing_I mean I'm afraid you do not have time to change14:00
zhubingbing_;)14:00
sdakezhubingbing_ iv'e committed to working on this today14:00
zhubingbing_nice14:00
sdakezhubingbing_ lets take my commitments one day at a time this week - i've been on work travel for 2 weeks so need to catch up a bit14:00
sdakebut feel I can commit atleast today to doing the rework on thedoc14:01
*** lamt has joined #openstack-kolla14:01
zhubingbing_;)14:01
sdakeneed reviews :)14:02
*** jmccarthy has left #openstack-kolla14:02
*** jtriley_ has joined #openstack-kolla14:03
zhubingbing_doning14:03
zhubingbing_sdake14:04
zhubingbing_https://review.openstack.org/#/c/439740/14:04
zhubingbing_need fix it ;)14:04
sdakezhubingbing_ if you want  to work on that - that would be great :)14:05
sdakezhubingbing_ python is your native language :)14:05
*** jtriley has quit IRC14:05
sdakezhubingbing_ and bash and ansible etc ;)14:05
*** lamt has quit IRC14:05
pomacegonzalez: recheck? ;)14:06
sdakesbezverk are you about?14:06
egonzalezpomac, about?14:07
pomacegonzalez: https://review.openstack.org/#/c/439468/ - your comment14:07
zhubingbing_;)14:07
zhubingbing_ok14:07
egonzalezpomac, is to gates to run again to see if all is green14:08
pomacegonzalez: ah, oki14:08
egonzalezpomac, the same issue I was having hehe, thanks for it ;)14:08
pomacegonzalez: no problem ;)14:08
sdakezhubingbing_ do you want some guidance on https://review.openstack.org/#/c/439740/ - as in where to get started?14:09
*** lamt has joined #openstack-kolla14:09
sdakezhubingbing_ the review is there with no context on why the gate is busted14:10
zhubingbing_i think it can;t find kolla-ansible patch14:11
*** lamt has quit IRC14:12
sdakezhubingbing_ right - the root of the problem is here:14:13
zhubingbing_yes14:14
mnasersdake (and anyone else), would you be interested to be listed as a volunteer under the dockerhub image publishing spec that im writing up for infra?14:14
mnaserinc0 perhaps?14:14
*** skramaja has quit IRC14:14
*** schwicht has joined #openstack-kolla14:15
*** mpansky has quit IRC14:16
sdakezhubingbing_ https://github.com/openstack/kolla-kubernetes/blob/master/tools/setup_gate_common.sh#L69-L7114:16
sdakemnaser i'm not sure i would be all that valuable for that effort tbh - inc0 did most of the work on the getting the registry into tarballs.oo14:17
zhubingbing_yes14:17
zhubingbing_http://paste.openstack.org/show/601021/14:17
zhubingbing_;)14:17
sdakemnaser kfox1111 also has deep context in tarballs.oo work14:17
sdakezhubingbing_ that needs to be changed to sudo pip install .14:18
*** lamt has joined #openstack-kolla14:18
sdakezhubingbing_ the symlinks in the gate cause that patch to fail14:18
sdakezhubingbing_ the solution is to install via pip - as our deployment docs recommend14:18
sdakemnaser i can provide credentials to the dockerhub account to those that need it14:18
sdakemnaser inc0 has credentials, however, we probably want a test credentials account14:19
sdakemnaser perhaps even a new org, as deleting images in docker hub is a huge pITA - requires clicking 200+ times14:19
zhubingbing_sdake we should pip install kolla-ansbile/  kolla/  kolla-kubernetes/14:19
zhubingbing_don't use pip install .14:19
sdakemnaser the new org would be for testing - so we can abandon it easily14:19
zhubingbing_;)14:19
nea1"Failed to start libvirt guest" http://termbin.com/2kjn anyone got an idea what could be wrong?14:20
sdakezhubingbing_ right!14:20
sdakezhubingbing_ i'll update the docs accordingly14:20
zhubingbing_https://review.openstack.org/#/c/447356/514:20
zhubingbing_i continue review it14:20
*** lamt has quit IRC14:21
sdakemnaser i can help guide a bit - but can't do any implementation work as I don't know how beyond the docker commands and creds and whatnot14:23
*** lamt has joined #openstack-kolla14:24
*** lamt has quit IRC14:24
sdakezhubingbing_ by the end of the week, i'd prefer to have our gate in sync with our deploy docs14:27
zhubingbing_emm14:28
zhubingbing_yes14:28
sdakezhubingbing_ this means merging https://review.openstack.org/#/c/439740/ which I am not sure if i can get to14:28
sdakezhubingbing_ asking someone to cherrypick a patch in a deployment doc is kind of - well not ideal :)14:28
sdakezhubingbing_ we can't merge https://review.openstack.org/#/c/439740/ if the gates are red14:29
zhubingbing_so we should modify gate ?14:29
sdakezhubingbing_ yes - by removing symlinks and changing to:14:30
sdake[07:19:50]  <zhubingbing_>sdake we should pip install kolla-ansbile/  kolla/  kolla-kubernetes/14:30
zhubingbing_hmm i try do it ;)14:30
sdakezhubingbing_ I suspect this will entail alot of rework of the gate scripts14:30
zhubingbing_yes14:31
sdakefinally ejected lastpass from my life14:33
sdakeportdirect ^^14:34
mnasersdake inc0 anyone interested in dockerhub publishing of images -- please review kindly - https://review.openstack.org/#/c/447524/14:34
zhubingbing_kolla-k8s have supporting placement api in master14:35
zhubingbing_https://github.com/openstack/kolla-kubernetes/commit/b89e1136aa082e47d29a23ee542a89dc7b703efa14:36
spsuryasdake:  would be great, if you take a look on the drafted BP for kolla-k8s. https://blueprints.launchpad.net/kolla-kubernetes/+spec/stabilization-unittest-coverage-improvement14:36
spsuryasdake: provide your views on this and approve the same, if it feasible.14:37
*** mpansky has joined #openstack-kolla14:38
sdakemnaser reviewed14:39
*** duke__ has quit IRC14:41
zhubingbing_sup kfox14:43
sdakespsurya needs an assignee to be approved14:43
zhubingbing_sup kfox111114:43
sdakespsurya however will approve once there is an assignee :)14:43
sdakespsurya note i moved the work items to the correct location in launchpad14:43
zhubingbing_sup sbezverrk14:44
spsuryasdake:  thanks14:44
sdakesbezverk is the nick zhubingbing_ :)14:44
zhubingbing_our kolla-k8s gate is deploy in 2.0.214:44
zhubingbing_;)14:44
sdakezhubingbing_ the gate actually deploys 2.0.2 and 3.0.214:44
zhubingbing_ok14:45
sdakezhubingbing_ i'd leave that alone during the gate rework - will probably just confuse the patch work on https://review.openstack.org/#/c/439740/14:45
zhubingbing_so we install kolla-ansible ocata version ?14:45
sdakezhubingbing_ yup14:45
*** saneax is now known as saneax-_-|AFK14:46
sdakezhubingbing_ actually master14:46
*** lamt has joined #openstack-kolla14:46
sdakekolla-ansible is needed for genconfig14:46
sdakewe want to install mater of kolla-ansible to get the latest fixes for generating configuration14:46
sdakezhubingbing_ I know this creates some chaos with 2.0.2 images14:46
zhubingbing_so https://github.com/openstack/kolla-kubernetes/blob/master/tools/setup_gate_common.sh#L80L9214:46
zhubingbing_OK14:47
sdakezhubingbing_ after we finish this doc, we are ejecting kolla-ansible entirely from the code base14:47
sdakezhubingbing_ that is the next blueprint of essential nature14:47
zhubingbing_yes14:48
sdakedoc essential blueprint, external-configmaps essential blueprint14:48
spsuryasdake: After kolla-k8s dev env setup, i will assign it to myself and will start adding the missing one.14:48
spsuryasdake: thanks for placing it to right place14:48
sdakespsurya cool - you can assign yourself now and I can approve the blueprint then or ping anyone in the kolla-kubernetes-drivers group later once your ready to approve the blueprint14:49
mnasersdake rewrite that paragraph14:49
mnaserrewrote*14:49
*** jtriley_ has quit IRC14:51
sdakemnaser LGTM14:52
mnasercool, ill wait for a bit more info from folks here and then throw it to -infra14:52
*** lamt has quit IRC14:54
*** lamt has joined #openstack-kolla14:56
*** lamt has quit IRC14:57
*** jtriley has joined #openstack-kolla14:59
jaosorioris this the right place to ask kolla-ansible questions?15:01
jaosoriorI had done a deployment in my local machine with just mariadb and keystone. Decided to do a kolla-ansible destroy; rebuilt my images, and now that I try again, I get the following error: https://paste.fedoraproject.org/paste/tp1-k5m4E8J6TMSlAxgNwV5M1UNdIGYhyRLivL9gydE=  which is pretty strange, since I did build the kolla-toolbox container image :/15:04
*** lamt has joined #openstack-kolla15:04
*** mnasiadka has quit IRC15:05
mnaser2 easy ones missing a +w https://review.openstack.org/#/c/446701/ and https://review.openstack.org/#/c/447226/15:05
*** lamt has quit IRC15:06
spsuryasdake: ok15:07
sdakejaosorior indeed it is the right place - wrong time possibly :)15:08
zhubingbing_sup <egonzalez15:08
openstackgerritzhubingbing proposed openstack/kolla-ansible master: Fix can't find /usr/lib/libCryptoki2_64.so in barbican  https://review.openstack.org/44456115:08
zhubingbing_sup egonzalez15:08
egonzalezzhubingbing_, hey15:08
zhubingbing_ https://review.openstack.org/44456115:09
sdakejaosorior can you run docker images | fpaste15:09
zhubingbing_;)15:09
zhubingbing_can u look it ?15:09
egonzalezjaosorior, also `docker volume ls` with no kolla image running15:09
sdakejaosorior and a rpm -qi docker-engine | fpaste15:10
zhubingbing_i am teseting magnum15:10
jaosoriorsdake: docker images -> https://paste.fedoraproject.org/paste/TyRm31dUplOO0uINxZwka15M1UNdIGYhyRLivL9gydE=/15:11
sdakejaosorior image is built correctly15:12
egonzalezzhubingbing_, there is not any 32-byte base64 passwd generator at generate passwords script15:13
zhubingbing_;)15:13
zhubingbing_so15:13
jaosoriorsdake: docker engine info https://paste.fedoraproject.org/paste/t-6HSdsRjUT4zqaJ7T3HBl5M1UNdIGYhyRLivL9gydE=15:13
zhubingbing_should i  how to modify15:13
zhubingbing_;)15:13
*** mnasiadka has joined #openstack-kolla15:13
egonzalezzhubingbing_, by default will create a uuid passwd, barbican expect a 32byte base64, tho15:13
jaosorioregonzalez: docker volume ls -> https://paste.fedoraproject.org/paste/To7YaWXima9G83oOztJdgF5M1UNdIGYhyRLivL9gydE=/15:15
mnaserpbourke https://review.openstack.org/#/c/447226/ goof'ed on the original change, this one is tested in prod :(15:15
zhubingbing_hmm we don't add it kek = '{{ barbican_crypto_password }}15:15
sdakeDaviey_ can you review https://review.openstack.org/#/c/447226/1 and validate it is compliant with the stable backports policy?15:15
zhubingbing_right ?15:16
*** saneax-_-|AFK has quit IRC15:16
egonzalezjaosorior, hrm, i think the issue is with devicemapper and docker 1.13.6, for some reason when tries to restart the container devicemapper still blocking devices and fail to restart but removes the container15:17
*** mnasiadka has quit IRC15:17
egonzalezjaosorior, if try again with no kolla-toolbox container running should work fine15:17
sdakeegonzalez you mean 1.12.6 in fedora?15:18
jaosorioregonzalez: right, so currently kolla-toolbox is not running. And yet I still get that error :/15:18
sdakejaosorior there are lots o problems with devicemapper as a storage backend15:19
sdakejaosorior i'd recommend btrfs - this is somewhere in our documentation - moment let me find it15:19
egonzalezsdake, didnt check the version paste :(15:19
mnaserif you use devicemapper15:19
mnaseryou have to set it up properly15:19
mnaserhttp://www.projectatomic.io/blog/2015/06/notes-on-fedora-centos-and-docker-storage-drivers/15:20
mnaserxfs+overlayfs will cause problems (learned that one myself)15:20
jaosoriorI was just using the defaults. If there is something I should be using instead, I can change it.15:20
sdakemnaser are you using lvm in your deployment?15:21
mnaserdocker info should tell you which drive you're using15:21
*** crushil has quit IRC15:21
*** lamt has joined #openstack-kolla15:22
mnasersdake https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/#configure-docker-with-devicemapper > "Configure direct-lvm mode for production"15:23
*** lamt has quit IRC15:23
nea1how do I disable keepalived / haproxy? (for the all-in-one setup)15:25
mnaserenable_haproxy: false15:25
mnaserin globals.yml15:25
jaosoriormnaser: thanks for the link; I'm attempting to use overlayfs instead15:26
mnaserjaosorior overlayfs was broken for me15:27
mnasermariadb fails to install15:27
mnaserwait actually15:27
mnaserthe problems were only happening in build time15:27
mnaserso maybe you'll be okay in deploy15:27
jaosorioroh15:27
jaosoriorwas attempting to rebuild the images15:27
jaosoriorwell, lets see how that goes15:27
kfox1111morning.15:28
*** manheim has quit IRC15:28
mnasero/ kfox111115:29
*** mnasiadka has joined #openstack-kolla15:29
mnaserkfox1111 love to hear your input on this - https://review.openstack.org/#/c/447524/ :)15:29
kfox1111hey mnaser.15:32
kfox1111sure. sec15:32
nea1mnaser: strange, why isn't it in there (commented out like with all other things that are available?)15:33
*** mnasiadka has quit IRC15:34
nea1but thanks :)15:34
*** hrw has quit IRC15:35
*** lamt has joined #openstack-kolla15:35
kfox1111mnaser: looks good to me.15:35
*** hrw has joined #openstack-kolla15:36
*** mnasiadka has joined #openstack-kolla15:37
jaosoriormnaser: had the same issue with overlayfs15:41
*** mnasiadka has quit IRC15:42
thomas_oneillwhat's the process for a bug in kolla that ends up being a bug in another project?15:43
thomas_oneillwell not even a 'bug', just something that needs changing... Like if I need to submit a PS to bifrost to change some stuff, can we still do Depends-On for stuff in other projects?15:43
thomas_oneillah yeah surely we can because I could do that from kolla-ansible to kolla, so yeah, nevermind, ignore me15:43
*** lamt has quit IRC15:44
*** jaosorior has quit IRC15:45
*** matrohon has quit IRC15:46
*** mpansky has quit IRC15:46
*** lamt has joined #openstack-kolla15:47
*** mnasiadka has joined #openstack-kolla15:47
*** lamt has quit IRC15:50
*** matrohon has joined #openstack-kolla15:50
*** mnasiadka has quit IRC15:52
*** lamt has joined #openstack-kolla15:52
*** blallau has quit IRC15:54
*** sayantani01 has joined #openstack-kolla15:55
*** mpansky has joined #openstack-kolla15:55
*** mnasiadka has joined #openstack-kolla15:57
*** jaosorior has joined #openstack-kolla15:59
*** mnasiadka has quit IRC16:01
*** iceyao has joined #openstack-kolla16:02
nea1mnaser: "TASK [haproxy : Checking if kolla_internal_vip_address and kolla_external_vip_address are not pingable from any node] ***" is failing, after I disabled haproxy in the globals.yml16:07
nea1while running the prechecks16:07
*** manheim has joined #openstack-kolla16:08
thomas_oneillnea1: can you ping the address you've specified for those vars?16:09
*** rmart04 has quit IRC16:09
jaosoriorsdake: what was the documentation for the btrfs configuration? Still haven't gotten my setup to work :/16:10
*** tonanhngo has joined #openstack-kolla16:10
thomas_oneilloh sorry I re-read what you put16:10
*** crushil has joined #openstack-kolla16:10
thomas_oneillnea1: you're using the kolla-ansible binary, right? do a: which kolla-ansible16:10
thomas_oneillnea1: if you want to run the kolla-ansible using the playbooks in your working directory, you need to run tools/kolla-ansible16:11
*** jmccarthy has joined #openstack-kolla16:12
*** iceyao has quit IRC16:12
thomas_oneillnea1: but yeah you need to be aware of how you've installed these binaries and what code they are actually running16:12
sdakeja09:12:29]  <sdake>jaosorior did you change your docker config to use direct-lvm?16:13
sdake[09:12:39]  <sdake>jaosorior if not, i'd start there first16:13
*** lamt has quit IRC16:13
jaosoriorsdake: I didn't. I went for the overlayfs option16:13
openstackgerritzhubingbing proposed openstack/kolla-ansible master: Fix can't find /usr/lib/libCryptoki2_64.so in barbican  https://review.openstack.org/44456116:14
*** lamt has joined #openstack-kolla16:14
sdakejaosorior note if you change the docker engine storage driver, you need to sudo systemctl stop docker; rm -rf /var/lib/docker; sudo systemctl start docker- note this will erase all of your built images and you will have to build again16:14
jaosoriorsdake: I did16:15
jaosorioryep16:15
jaosoriorremoved everything16:15
jaosoriorrebuilt my images16:15
jaosoriorand still got the same error16:15
openstackgerritzhubingbing proposed openstack/kolla-ansible master: Fix can't find /usr/lib/libCryptoki2_64.so in barbican  https://review.openstack.org/44456116:16
sdakejaosorior run docker info16:16
sdake-> fpaste16:16
jaosoriorsdake: Storage Driver: overlay16:16
*** saneax-_-|AFK has joined #openstack-kolla16:17
sdakedid yo ustop docker prior to the rm -rf?16:17
jaosoriorsdake: https://paste.fedoraproject.org/paste/DAkn3Oc3jUtXTSE1zMUu015M1UNdIGYhyRLivL9gydE=/16:17
jaosoriorsdake: yes16:17
sdakejaosorior note - fedora 25 is an unsupported host - kolla may or may not work - need more context however on your failure16:18
sdakejaosorior you were able to get through one deployment correct?16:19
jaosorioryep16:19
*** lamt has quit IRC16:19
jaosoriorthe first one16:19
sdakeyou destroyed?16:19
jaosoriorI did16:19
sdakeyou deployed and that failed?16:19
jaosoriorcorrect16:19
jaosoriorIf I may add, I did a destroy including the images16:19
sdakeyou changed the docker storage driver as per recommendations?16:19
sdakeroger16:19
sdakeat any point did you reboot your host16:20
jaosoriorsdake: yep; used to be devicemapper, and I switched it to overlayfs16:20
jaosoriorsdake: haven't16:20
sdakeok - i'd give that a spin as painful as that may be16:20
sdakethen try deploy destroy deploy with overlayfs16:20
sdakei speculate that the kernel has some lost references on /var/lib/docker - devicemapper does that16:20
sdakewhen switching from devicemapper a reboot is always required16:21
sdakei'm surprised you were able to rm -rf /var/lib/docker at all without errors16:21
jaosoriorI'll try that16:21
jaosoriorthanks16:21
hrwkolla on f25... wfm16:23
openstackgerritzhubingbing proposed openstack/kolla-ansible master: Fix can't find /usr/lib/libCryptoki2_64.so in barbican  https://review.openstack.org/44456116:23
*** pcaruana has quit IRC16:27
*** lamt has joined #openstack-kolla16:28
*** jrich523 has quit IRC16:29
nea1thomas_oneill:  When running an All-In-One16:29
nea1 28 # without haproxy and keepalived, this should be the first IP on your16:29
nea1 29 # 'network_interface' as set in the Networking section below.16:29
nea1so it was the IP from my first interface16:30
*** rwellum has quit IRC16:30
thomas_oneillnea1: yeah sorry I read what you put too fast and then corrected myself. It shouldn't have been running those checks if you disabled haproxy, so you must be running some installed binary that isn't looking at the playbooks/vars that you've amended.16:32
thomas_oneillnea1: if you pip install kolla-ansible or pip install . in the kolla-ansible directory, it will install all those playbooks and vars hard-coded into your python environment16:33
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: Fernet Token Support  https://review.openstack.org/44627416:34
openstackgerritMerged openstack/kolla stable/newton: Turn on SSH for Keystone for all distros.  https://review.openstack.org/44722616:35
sdakehrw good to hear :)16:37
hrwsdake: 1094 images built. centos, debian, ubuntu. binary and source16:37
*** zhubingbing_ has quit IRC16:38
openstackgerritMerged openstack/kolla-ansible master: Enable heat-api proxy header parsing  https://review.openstack.org/43946816:38
*** lamt has quit IRC16:40
sdakehttps://github.com/openstack/kolla - 42 releases16:41
sdake3 meals a day for 2 weeks - thats the diet i'm on :)16:41
*** lamt has joined #openstack-kolla16:41
hrw;)16:43
hrwbtw - how to list tags on image present in repo?16:43
*** lamt has quit IRC16:43
hrwinstead of 'docker pull --all imagename' and then looking at output16:43
*** lamt has joined #openstack-kolla16:48
nea1thomas_oneill: I did pip install kolla-ansible16:48
*** bmace has quit IRC16:48
*** MasterOfBugs has joined #openstack-kolla16:49
nea1but I now solved it differently, I created a bridge with I'm using as network device so I can have a nated network there16:49
*** bmace has joined #openstack-kolla16:49
*** lamt has quit IRC16:49
*** jaosorior has quit IRC16:50
thomas_oneillnea1: well that's great but it's still definitely worth being aware of what code you're actually running ;)16:51
*** jaosorior has joined #openstack-kolla16:52
nea1thomas_oneill: well I'll have a look at it later, I'm kind of lacking time, and if it now builds then it'll be fine for not16:53
*** Serlex has quit IRC16:55
*** manheim has quit IRC16:56
nea1ever tried using a bridge as network_interface which contains a "-" e.g. "br-mgmt"?16:57
thomas_oneillextremely unlikely that the - will make any difference16:58
srwilkersmorning16:58
thomas_oneillthe fact that a bridge is a different kind of network interface than a regular physical network interface is far more likely to be the problem with that nea116:58
jascott1mornin' srwilkers16:58
nea1ansible facts will have it as "ansible_br_mgmt" not "ansible_br-mgmt" https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/prechecks/tasks/port_checks.yml#L816:58
thomas_oneillokay but is it moaning about something?16:59
nea1thomas_oneill: with the neutron network yes for sure, but is it trying to bridge network_interface as well? I think it only adds an IP to it (the vip IP)16:59
*** unicell1 has quit IRC17:00
nea1thomas_oneill: yep, as it can't find it in the dict - ['ansible_' + api_interface | regex_replace('-', '_')] fixes it17:00
*** egonzalez has quit IRC17:00
*** zhubingbing has joined #openstack-kolla17:00
srwilkerssup jascott117:00
thomas_oneilloh I see17:01
nea1but that will have to be done on more places than just there - I'll go over it later for now I'm moving to non "-" containing bridges17:01
nea1I'll open a bug ticket with a patch or so tomorrow17:03
zhubingbinggood night ;) guys17:06
zhubingbingbye17:06
qwangsdake: hi17:07
sdakeqwang would you mind reviewing the deployment guide now in gerrit plz17:07
sdakeqwang want to remove the cruft - will git review a new rev after you do a review17:08
qwangsdake: my pleasure17:08
jaosoriorsdake: rebooting did the trick! thanks!17:11
nea1I'll be gone too for today, thanks so far for the help17:11
jaosoriormnaser: also, it seems that overlayfs worked; was able to start the mariadb container.17:12
openstackgerritzhubingbing proposed openstack/kolla-ansible master: Fix can't find /usr/lib/libCryptoki2_64.so in barbican  https://review.openstack.org/44456117:12
v1k0d3ni think some folks may have asked portdirect about an updated a v1.5.2 kube-controller-manager for halcyon...that's been updated for anyone who's interested.17:13
sdakethanks qwang17:13
v1k0d3nmorning/afternoon y'all :)17:14
sdakev1k0d3n i think we are on to 1.5.4 or 1.5.3 now - not sure ;)17:14
v1k0d3nif you guys run into issues, please let me know.17:14
*** matrohon has quit IRC17:14
v1k0d3nok sdake...i think someone out there wanted a v1.5.2....so i guess this applies to them.17:15
sdakev1k0d3n halcyon needs this image iiuc - and we would like our docs to be in sync with our dev env and gate17:16
*** eaguilar has joined #openstack-kolla17:16
mnaseri had the issue during build time so that might be it jaosorior17:20
v1k0d3nsdake, not sure what you're asking.17:21
sdakev1k0d3n bbiaf17:21
v1k0d3nif you ever need an update to the image...just submit a PR; that'll keep things in sync. i'm in the process of creating a v1.5.4 image now as well (since you mentioned it). always willing to assist the kolla folks. 👍🏼17:24
srwilkersfor what it's worth, if anyone notices we need an updated image or finds any other issues with halcyon, it'd be great if they could file an issue against halcyon proper so we can address it in a timely manner.17:24
srwilkerswhat v1k0d3n said17:25
v1k0d3naaaaand what srwilkers said too 😃17:25
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: Fernet Token Support  https://review.openstack.org/44627417:26
v1k0d3nwe don't really use halcyon much anymore, so we're probably not going to find as many issues as you guys.17:26
*** mpansky has quit IRC17:26
*** unicell has joined #openstack-kolla17:27
*** jaosorior has quit IRC17:35
openstackgerritAlicja Kwasniewska proposed openstack/kolla-ansible master: [WIP] Added playbooks for snap deployment  https://review.openstack.org/44616517:36
*** iceyao has joined #openstack-kolla17:36
*** lazyPwr is now known as lazyPower17:37
*** rwellum has joined #openstack-kolla17:37
*** lazyPower has quit IRC17:38
*** lazyPower has joined #openstack-kolla17:38
hrwargh17:38
hrwfscking bifrost17:39
inc0:D17:39
inc0all the love17:39
inc0kfox1111 sbezverk around17:39
inc0?17:39
kfox1111inc0: hey17:42
*** jmccarthy has quit IRC17:42
hrwwhenever fails fail for me I check for bifrost-base. like http://logs.openstack.org/40/430940/26/check/gate-kolla-dsvm-build-ubuntu-source-ubuntu-xenial/a33c9d8/console.html#_2017-03-20_16_53_12_325149 or http://logs.openstack.org/40/430940/26/check/gate-kolla-dsvm-build-centos-source-centos-7/2c6c11f/console.html#_2017-03-20_17_27_01_38708717:42
*** zhubingbing has quit IRC17:42
inc0kfox1111: correct me if I'm wrong, but these instructions are pre-helm right? https://review.openstack.org/#/c/447356/217:43
sdakev1k0d3n I was a bit cryptic earlier - had meeting - what i think kolla needs is that controller built for every version of kubernetes17:43
*** masber has quit IRC17:43
sdakev1k0d3n our gate builds its own controller for ceph - our docs reference version 1.5.2 (iirc) and we need the dev env = deploy guide = gate for versions17:44
v1k0d3nyeah ok. well, let me know if you need an updated controller-manager, or your welcome to submit a PR.17:45
v1k0d3nsuper easy :)17:45
sdakev1k0d3n sounds good17:45
sdakev1k0d3n i don't know yet - and dont want to waste your time with frivilous requests :)17:45
v1k0d3nwell...right now, people are going to invididual teammembers on our side, rather than just submitting a PR or issue.17:46
kfox1111inc0: the pointed at etherpad is https://etherpad.openstack.org/p/kolla-service-start17:46
v1k0d3nthat actually takes more time.17:46
*** masber has joined #openstack-kolla17:46
v1k0d3nanyway...i gotta run. don't have a lot of time to chat.17:46
v1k0d3nlater17:46
sdakev1k0d3n the workflow wasn't defined for building the controller - however we can disemminate that information to the various parties involved17:46
inc0right, I missed that, I'll move this to change17:47
sdakeinc0 your moving that etherpad where - to the review?17:49
inc0yeah, all that stuff needs to land in review17:50
inc0we can't link etherpads...17:50
sdakeinc0 agreed i have a review in place here: https://review.openstack.org/#/c/447356/ - please review and i'll address17:50
sdakeinc0 if folks provide their reviews in next 1 hour, i'l address all comments - spin the  review - then spin the review again converted to RST17:51
kfox1111gnocchi's trying to leave the union. fasinating..17:53
inc0now we need to find good name17:53
inc0gnout?17:53
kfox1111:)17:54
kfox1111" 3+17:55
kfox1111node clusters with reliable network"17:55
kfox1111what does that mean?17:55
sdakekfox1111 context?17:56
kfox1111the thread "[openstack-dev] [kolla] rabbitmq cluster_partition_handling config in kolla-ansible"17:56
kfox1111what is a "reliable network" though.17:56
kfox1111not sure I've seen one yet.17:56
inc0lol17:57
* hrw -> checking where centos images failed17:57
kfox1111stuff fails. those who assume it won't  get to keep the pieces when it breaks.17:57
openstackgerritAlicja Kwasniewska proposed openstack/kolla master: Added snap-telemetry container  https://review.openstack.org/44616417:58
sdakekfox1111 i think you just answered your own question or his :)17:58
kfox1111yeah17:58
*** duke__ has joined #openstack-kolla17:59
hrwkfox1111: I know why it fails. have to check which images17:59
sdakekfox1111 it appears rabbitmq thinks reliable networks are a thing - when your opinion is they are not17:59
kfox1111sdake: yeah. I know their opinion. and thats why so many ops have turned off clustering after a while of using it.18:00
sdakeqwang would you mind adding a -1 to https://review.openstack.org/#/c/447356 so I can track which comments need attention?18:00
kfox1111if you design a system off a flawed assumption, badness ensues. :/18:00
kfox1111every summit we go around asking folks their experience with rabbit clustering... hoping to hear a different answer. :/18:01
inc0I talked with Mirantis ops once and if they experienced net partition, they just wipe rabbit clean and restart it with message loss18:02
qwangsdake: sure. no reason to reject this kind of requests, I think.18:02
kfox1111inc0: yeah. that works if you don't value the data. :/18:03
kfox1111for rpc, its generally fine.18:03
sdakeqwang typically you would -1 vote if you see a problem with a review, so the submitter knows you object to the doc/code/etc18:03
kfox1111if you really want to get event data out though, that can be a problem.18:03
inc0agree18:03
kfox1111for some of the stuf we do, we do care. :/18:05
*** masber has quit IRC18:05
*** ccesario has joined #openstack-kolla18:06
sdakekfox1111 sbezverk can i get one review out of you int he next 30 minutes: https://review.openstack.org/#/c/447356/5/doc/source/deployment-guide.rst18:07
*** mgoddard has quit IRC18:07
sdakeinc0 mnaser had a question for you earlier whether you wanted to participate in the creation of the docker push infrastructure blueprint18:07
sdakeinc0: http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2017-03-20.log.html#t2017-03-20T14:14:2418:08
*** athomas has quit IRC18:09
sdakeinc0 can you review more than lines 1-42 of the document, there are many other problems with the document as it stands18:09
inc0sdake: I still work on it18:10
inc0these are issues I see right now18:10
sdakeinc0 roger - thought you were done18:10
sdakeinc0 there are other links to etherpad which need migration as well18:10
kfox1111sdake: why force override all the defaults?18:11
sdakekfox1111 ask the question in the review - I have no idea why its that way - perhaps another reviewer can answer, such as sbezverk  :)18:11
kfox1111its in an etherpad though.18:11
sdakekfox1111 what i'd like to know is how to generate cloud.yaml in the review18:11
kfox1111I guess I could generally comment though...18:11
sdakekfox1111 you can comment on the line that links to the etherpad - that owuld be helpful18:11
kfox1111sdake: shjouldh't have to generate it. onlyu specify the stuff that deviates from default.18:12
kfox1111k18:12
sdakekfox1111 I have no idea what should deviate from defaults - that was the cloud.yaml sbezverk handed me in a paste in irc18:12
kfox1111ah. ok.18:12
sdakekfox1111 this question is important to answer there is a TODO(sbezverk) I added there - however - i think he was traveling and didn't answer it - perhaps you could18:13
sdakeend goal: merge this document prior to friday since it was first demoed on feb 15th, over a month ago ;)18:14
kfox1111I can't identify further customizations unless I get time to actually try deploying.18:14
kfox1111If its working though, its working?18:14
*** duke__ has quit IRC18:17
*** adrian_otto has joined #openstack-kolla18:17
inc0kfox1111: qq - are you going to Boston?18:20
kfox1111yeah.18:22
inc0wanna join me on stage with kolla-k8s update?;)18:22
inc0I ninja-added your name when I was asked for co-presenters, but that's totally fine to remove it :)18:23
inc0just making sure18:23
kfox1111maybe.18:23
inc0think about it and let me know when you know plz18:23
inc0I can run whole thing myself18:23
inc0bbiaf, need some food18:25
kfox1111k. will do.18:25
*** crushil has quit IRC18:26
*** vhosakot has joined #openstack-kolla18:30
*** crushil has joined #openstack-kolla18:34
sdakevhosakot can you please provide a review of https://review.openstack.org/#/c/44735618:41
vhosakotsure, will do, thanks for the link sdake18:42
sdakethanks vhosakot18:42
*** mgoddard has joined #openstack-kolla18:43
*** iceyao has quit IRC18:46
mnaserhttps://review.openstack.org/#/c/447524/ inc0 id appreciate your thoughts on this and anyone else is welcome before i make another revision for infra folks18:46
*** crushil has quit IRC18:50
*** david-lyle_ has joined #openstack-kolla18:52
*** david-lyle has quit IRC18:52
*** david-lyle_ is now known as david-lyle18:53
*** lamt has joined #openstack-kolla18:55
*** jemcevoy has joined #openstack-kolla18:55
*** eaguilar has quit IRC18:56
*** masber has joined #openstack-kolla18:58
*** lamt has quit IRC18:59
sbezverkinc0: sorry for delayed reply, have backlog from last week absence. what can I do for you?19:01
*** fooliouno has joined #openstack-kolla19:03
*** lamt has joined #openstack-kolla19:04
*** iceyao has joined #openstack-kolla19:04
*** crushil has joined #openstack-kolla19:05
*** lamt has quit IRC19:11
sbezverkkfox1111: ping?19:13
kfox1111ping19:13
kfox1111whats up? :)19:13
openstackgerritGraeme Seaton proposed openstack/kolla-ansible master: Allow alternative usernames for openstack in external-ceph  https://review.openstack.org/44765019:14
sbezverkkfox1111: have you every configured dhcp options for pools used by neutron dhcp server?19:14
kfox1111hmm...19:15
kfox1111globally, yes. but not for specific pools...19:15
kfox1111there was an option that got merged to do overrides per port.19:15
kfox1111and I think there was one in review to do it per subnet, but I lost track of that review, and I don't think it may have ever merged?19:15
sbezverkkfox1111: :( it seems there is a json command to configure it but I do not see any cli19:16
kfox1111well, thats not horible.19:16
kfox1111shoudl be able to wrap that up in a job?19:17
*** masber has quit IRC19:17
sbezverkkfox1111: yeah, but it is like a hack really19:20
kfox1111agreed. but its either that, or wait until the openstack cli catches up with reality. which can be a while sometimes. :19:21
kfox1111:/19:21
sbezverkkfox1111: got it, thanks.. will try it then..19:21
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: Fernet Token Support  https://review.openstack.org/44627419:24
*** lamt has joined #openstack-kolla19:24
openstackgerritGraeme Seaton proposed openstack/kolla-ansible master: Set fluentd output to elasticsearch  use elasticsearch_address  https://review.openstack.org/44765419:30
openstackgerritGraeme Seaton proposed openstack/kolla-ansible master: Set fluentd output to elasticsearch to use elasticsearch_address  https://review.openstack.org/44765419:32
*** lamt has quit IRC19:33
*** adrian_otto has quit IRC19:34
*** mpansky has joined #openstack-kolla19:35
*** crushil has quit IRC19:37
*** crushil has joined #openstack-kolla19:41
*** iceyao has quit IRC19:41
*** m1dev has quit IRC19:42
Daviey_sdake: It doesn't change config files, affects a significant amount of users.  Does expose a service that wasn't there before (but users would have EXPECTED it to be exposed)...  Minimal regression potential, i'd be happy to accept it19:42
*** krtaylor has quit IRC19:43
mnaserDaviey_ and especially given that the feature would literally be broken without it19:47
*** masber has joined #openstack-kolla19:50
*** lamt has joined #openstack-kolla20:00
*** rstarmer has joined #openstack-kolla20:01
*** rstarmer has quit IRC20:02
*** lamt has quit IRC20:04
*** satyar has quit IRC20:04
*** matrohon has joined #openstack-kolla20:12
*** masber has quit IRC20:13
*** dave-mcc_ has joined #openstack-kolla20:15
*** kencjohnston_ has joined #openstack-kolla20:15
*** pbourke_ has joined #openstack-kolla20:16
*** adrian_otto has joined #openstack-kolla20:17
*** zhenguo_ has joined #openstack-kolla20:18
*** esmiurium has joined #openstack-kolla20:20
*** srwilkers has quit IRC20:20
*** Aju has joined #openstack-kolla20:21
*** krtaylor has joined #openstack-kolla20:21
*** DuncanT_ has joined #openstack-kolla20:22
*** sdake_ has joined #openstack-kolla20:24
*** sdake_ has quit IRC20:24
*** sdake_ has joined #openstack-kolla20:24
*** spsurya__ has joined #openstack-kolla20:24
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: Fernet Token Support  https://review.openstack.org/44627420:24
*** jgriffith_ has joined #openstack-kolla20:27
sbezverkkfox1111: ping20:29
*** dave-mccowan has quit IRC20:29
*** pbourke has quit IRC20:29
*** shasha_t_ has quit IRC20:29
*** DuncanT has quit IRC20:29
*** aolwas has quit IRC20:29
*** spsurya has quit IRC20:29
*** sdake has quit IRC20:29
*** zhenguo has quit IRC20:29
*** kklimonda has quit IRC20:29
*** jgriffith has quit IRC20:29
*** alanmeadows has quit IRC20:29
*** afranc has quit IRC20:29
*** esmiurium_ has quit IRC20:29
*** kencjohnston has quit IRC20:29
*** spsurya__ is now known as spsurya20:29
kfox1111sbezverk: ping20:30
*** zhenguo_ is now known as zhenguo20:30
*** jgriffith_ is now known as jgriffith20:30
*** srwilkers has joined #openstack-kolla20:31
*** shardy has quit IRC20:32
sbezverkkfox1111: I am seeing strange thing, I have a linux bridge with ip address20:32
*** DuncanT_ is now known as DuncanT20:32
kfox1111yeah?20:33
sbezverkkfox1111: I can ping it, no prob20:33
sbezverkkfox1111: but when another container arp for ip assigned to the bridge20:33
*** kklimonda has joined #openstack-kolla20:33
*** dave-mcc_ is now known as dave-mccowan20:33
sbezverkit does not reply to arp requests, I can see them with tcpdump right on that bridge20:33
kfox1111iptables enabled?20:34
kfox1111iptables by default affects linuxbridge packets, but not ovs bridge packets.20:34
kfox1111stp being on might effect things too, if its a recently brought up port.20:34
sbezverkkfox1111: well it is basic kube cluster running openstack20:34
sbezverkand ironic20:34
kfox1111in the gate?20:34
sbezverkcontainer in question runs in net=host mode20:34
kfox1111hmm....20:35
sbezverkkfox1111: no, had to move from the gate, was close to impossible to troubleshoot at it reuired packet captures20:35
kfox1111so, container net=host arps fine, container net != host on the same host fails?20:35
sbezverkkfox1111: I tcpdump in the container with net=host  and I can see arp request packets20:36
kfox1111yeah, I get that. this level of deep network inspection would be tricky that wya.20:36
sbezverkby some reason nothing replies to arp request, not even host which I think it shold20:36
kfox1111ok... so, let me double check:20:37
kfox1111you have a single host.20:37
kfox1111on the host, you have a linux bridge.20:37
kfox1111you put an ip address on that linux bridge.20:37
sbezverkkfox1111: yes20:38
kfox1111you launch a container on the host, net=host, then try and ping the linux bridge's address.20:38
sbezverkkfox1111: not exactly20:38
kfox1111and you can tcpdump the bridge and see the arp from the container,20:38
kfox1111but not the response?20:38
kfox1111ok. whats different?20:38
sbezverkkfox1111: I can ping from the container in net=host20:38
sbezverkbut I have my "baremetal" vm whcih is also plugged into this bridge20:38
*** Pavo has joined #openstack-kolla20:39
*** shardy has joined #openstack-kolla20:39
sbezverkand it is my baremetal vm arping for that ip since it is ip of tftp server20:39
sbezverkto download pxelinux.020:39
*** jtriley has quit IRC20:39
sbezverkI see arp requests coming from that VM but nothing responds to them20:39
sbezverkkfox1111: http://paste.openstack.org/show/603495/20:40
sbezverk.10 is ip address of tftp server .104 is ip address which neutron dhcp server gave to my baremetal VM20:41
kfox1111oh, so... two boxes? or 1?20:42
sbezverksorry .10320:42
kfox1111(vm's or otherwise)20:42
sbezverkone box20:42
kfox1111two containers?20:42
sbezverkone physcial box may VMs20:42
kfox1111oh. k.20:42
sbezverkone container and one vm20:42
kfox1111hmm...20:42
sbezverkpxe is ironic container20:42
sbezverkvm-1 is baremetal vm20:42
kfox1111k.20:42
kfox1111what launched the vm?20:42
sbezverkI am simulating baremetal provisioning20:43
sbezverkvmbc20:43
sbezverkworks like a charm20:43
kfox1111so, libvirt?20:43
sbezverkvirtualbmc20:43
sbezverkyes vbmc contacts libvirt20:43
kfox1111virtualbmc -> libvirt -> kvm?20:43
sbezverkyep20:43
kfox1111k.20:43
kfox1111and the libvirt network backend is linuxbridge?20:43
kfox1111in bridging mode?20:43
sbezverkI can see vm comes up and gets ip address from neutron20:43
kfox1111ok. so dnsmasq is working.20:44
kfox1111hmm...20:44
sbezverkvm is configured to plg its interface into a specific linuxbridge20:44
kfox1111and thats in the container too?20:44
sbezverkyes20:44
sbezverkwhole neutron runs in containers20:44
kfox1111and that bridge has 172.21.0.10 on it?20:44
*** manheim has joined #openstack-kolla20:44
sbezverkyes20:44
*** Pavo has quit IRC20:44
sbezverkif you have time I can show you in webex20:45
kfox1111centos/ubuntu host?20:45
sbezverkcenits20:45
kfox1111um... yeah.20:45
sbezverkcentos20:45
kfox1111did you turn off iptables/firewalld?20:45
sbezverkfirewalld is off otherwise kube would not work20:45
kfox1111k. just double checking.20:45
sbezverkiptables I have not touched20:45
kfox1111and the tcpdump you gave is from the bridge?20:45
sbezverkit is controlled by openstack20:45
sbezverkyes20:46
kfox1111did the vm recently come up at that point, or was it running for more then a minute?20:46
sbezverkironic contacts vbmc - it brings up VM, VM gets ip addresss from neutron dhcp server then it gets tftp server ip in dhcp option and then it tries to download pxelinux.o from tftp20:48
sbezverkso I do not control much, everything is done by ironic20:48
kfox1111so if its getting the ip first, then its not STP on the bridge.20:49
sbezverkagree, it seems connectivity works20:49
sbezverkhttps://cisco.webex.com/join/sbezverk20:49
kfox1111anything in /etc/sysconfig/iptables?20:49
kfox1111k.20:49
sbezverkanybody who wants to join and see ironic in action are welcome20:49
*** unicell1 has joined #openstack-kolla20:51
*** unicell has quit IRC20:52
openstackgerritMohammed Naser proposed openstack/kolla master: Speed up builds by increasing threads for builds  https://review.openstack.org/44670120:56
mnaseri had to rebase this patch so i lost my +W .. any cores? ^ <320:56
*** rhallisey has quit IRC21:00
*** Pavo has joined #openstack-kolla21:08
jemcevoySamYaple:  you there21:10
*** crushil has quit IRC21:12
*** Pavo has quit IRC21:16
*** hawi has quit IRC21:16
*** hawi has joined #openstack-kolla21:17
*** goldyfruit has quit IRC21:24
*** schwicht has quit IRC21:29
*** srwilkers has quit IRC21:30
*** Jeffrey4l_ has quit IRC21:35
*** manheim has quit IRC21:35
*** jrobinson has joined #openstack-kolla21:35
*** Pavo has joined #openstack-kolla21:37
*** shardy has quit IRC21:37
*** Jeffrey4l_ has joined #openstack-kolla21:38
*** Pavo has quit IRC21:39
*** rwellum has quit IRC21:47
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Fix Telegraf startup config files issue  https://review.openstack.org/44738221:48
*** matrohon has quit IRC21:49
mnaserugh21:51
mnaserbifrost broke gate again21:51
*** vhosakot has quit IRC21:53
jemcevoyinc0:  Is there a way for me to run kolla deploy on just one host?  maradb is dead on controller2 and I want to delete the mariadb container, image and volume and just deploy on controller2.21:53
jemcevoyI am running 3.0.2 in production/21:54
inc0jemcevoy: so in general re-running kolla deploy shouldn't touch anthing besides things that needs changing21:55
inc0but when you run kolla-ansible deploy it will print out long ansible command21:55
inc0as first line of output21:55
inc0you can just use this long ansible command, they're equivalent21:55
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: Fernet Token Support  https://review.openstack.org/44627421:55
*** rwallner has quit IRC21:56
inc0and then you have all sorts of filtering/manipulations of ansible at your disposal21:56
jemcevoyand add --limit to the end right21:56
inc0that should do it21:56
jemcevoyGreat I can just scroll back to my last run over the weekend21:57
*** schwicht has joined #openstack-kolla22:01
sdake_inc0 biforst is not building - the gates are jammed up22:02
mnasersdake_ https://bugs.launchpad.net/kolla/+bug/167448322:02
openstackLaunchpad bug 1674483 in kolla "Bifrost failing because of missing SUDO_USER" [Undecided,New]22:02
sdake_inc0 as the gates are voting, no progress can be made22:02
inc0what changed?:/22:02
*** fooliouno has quit IRC22:02
mnaserim trying to figure it out if you want to help out22:02
mnaseransible_env.SUDO_USER is .. unset for some reason22:02
mnaserhttps://github.com/openstack/bifrost/commit/36e32ecdc26035ecd853f830b30d42827662a68a22:03
mnaserthis merged22:03
mnaserwhich is running that role which is failing22:03
mnaseri guess when this merged it broke things https://review.openstack.org/#/c/444820/22:04
mnaserbecause that role is now running regardless?  and i assume it didnt run before22:04
inc0mnaser: can you link me failing review?22:04
mnaser(didnt verify this, im speculating)22:04
mnaserinc0 https://review.openstack.org/#/c/446701/22:04
mnaseri put a bit of info in the bug i created22:05
mnaserim going to assume ansible_env.SUDO_USER is unset when running it locally22:05
sdake_mnaser why would that cause the build to fail?22:06
mnasersdake_ as part of bifrost installation it runs a set of ansible playbooks22:07
*** sdake_ is now known as sdake22:07
sdakei see22:07
mnaseri assume its meant to target a remote host so ansible_env.SUDO_USER is supposed to be set22:07
mnaseri think the problem is they should be using a lookup instead of referring to ansible_env directly22:07
*** schwicht has quit IRC22:08
*** leseb has quit IRC22:09
*** dave-mccowan has quit IRC22:12
mnaserok i think i know how to solve this in bifrost land22:12
mnaserthere is an existing default but the problem is the lookup22:13
*** Pavo has joined #openstack-kolla22:13
*** leseb has joined #openstack-kolla22:15
*** mgoddard has quit IRC22:15
*** Pavo has quit IRC22:16
inc0mnaser: makes sense22:17
* inc0 building locally22:18
mnaserwrote a patch inc022:18
mnaseri am submitting to bifrost soon22:18
*** alanmeadows has joined #openstack-kolla22:19
mnaserinc0 sdake https://review.openstack.org/44771322:20
mnaserim not sure if you can somehow cherry pick that and try building with it but i think itll fix things22:23
*** Pavo has joined #openstack-kolla22:23
*** Pavo has quit IRC22:25
*** sayantani01 has quit IRC22:28
mnaserspoke with ironic core folks22:31
mnaserthey'll merge once it passes22:31
mnaserand hopefully we can recheck and all is good22:31
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-ansible master: Updated from global requirements  https://review.openstack.org/44677222:31
sdakeportdirect about?22:34
*** Pavo has joined #openstack-kolla22:34
*** manheim has joined #openstack-kolla22:37
inc0kfox1111: sbezverk question - kollakube res create configmap mariadb ended up with error [Errno 2] No such file or directory: '/home/ubuntu/kolla/ansible/roles/neutron/defaults/main.yml'22:38
sdakeinc0 you ahve to cherrypick a patch for that to work22:38
inc0link plz22:38
kfox1111weird.22:38
inc0it is weird22:38
sdakehttps://review.openstack.org/#/c/447356/22:39
sdakesearch for "CHERRYPICK"22:39
inc0kfox1111: https://review.openstack.org/#/c/439740/22:40
inc0ok...different question22:41
inc0why does it even need kolla-ansible?22:41
sdakegenconfig22:41
inc0I already done that22:41
inc0I have configs generated22:41
inc0I just want to create configmap22:41
sdakedunno code probably has the asnwer :)22:42
inc0ok this is wrong22:42
sdakei thought you were asking why kolla-kubernetes needs kolla-ansible22:42
inc0I know that one22:42
inc0let me check what this tool even intends to do, because this should be pretty simple one liner to create configmap from existing file22:43
kfox1111sbezverk: echo "0" > /proc/sys/net/bridge/bridge-nf-call-iptables22:44
inc0how to turn off kernel module like a pro22:44
*** krtaylor has quit IRC22:45
*** masber has joined #openstack-kolla22:45
sdakethis needs an ack: https://review.openstack.org/#/c/447217/22:46
*** Pavo has quit IRC22:47
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: Fernet Token Support  https://review.openstack.org/44627422:57
inc0kfox1111: how horrible would it be if I'd create playbook to template all the configmaps/secrets?22:59
inc0because frankly all we need is something to read yaml and output kube resources22:59
inc0then you do kubectl create -f /path/to/dir22:59
kfox1111inc0: isn't that what kolla-ansible does today? :)23:00
inc0kfox1111: for kolla-k8s23:00
inc0and yes23:00
inc0it's extremally easy playbook23:00
inc0(already wrote piece of play for ceph secrets)23:00
*** alanmeadows has quit IRC23:00
*** alanmeadows has joined #openstack-kolla23:00
inc0in fact, from my perspective it would be great if I could just submit piece of ansible to do all the prework for kolla-k8s23:01
kfox1111ideally we'd just put the effort into getting it into helm.23:01
kfox1111not much extra work I think.23:01
sdakekfox1111 tend to agree23:01
sdakeexternal config maps ftw23:02
kfox1111yeah23:02
inc0I don't know how good helm is for reading local files and if golang have stuff like filters to base6423:02
kfox1111doesn't need to?23:02
inc0for secrets yeah23:02
kfox1111we just copy the kolla-ansible templates into the teplate dir, and tweak some stuff?23:02
inc0ahh you mean create full configs in helm?23:03
kfox1111yeah, secret would be the exception. though there isn't many of those.23:03
kfox1111yeah.23:03
kfox1111helm install neutron-configmap23:03
*** rwallner has joined #openstack-kolla23:03
inc0well yes and no, it won't be that easy23:03
inc0we'd need to copy all the values from ansible too23:04
sdakeyup - that needs to be done23:04
inc0yes I know23:04
inc0but playbook I'm talking about is 1 day of work23:04
inc0then creating secrets+configmaps will be ansible-playbook  and kubectl23:05
inc02 commands23:05
inc0anyway, I'll do it anyway23:06
inc0because we need more robust tooling for that23:06
inc0and after that we can move configs to helm one by one23:06
inc0it's not going to be *that* easy23:06
inc0especially with overrides and shit23:06
*** rwallner has quit IRC23:08
kfox1111why would that be easier then just using genconfig?23:10
*** jrobinson has quit IRC23:11
inc0kfox1111: I'm using genconfig23:12
inc0I'm talking about kollakube resource configmap create replacement23:12
kfox1111oh.23:12
inc0I don't see much value in this pseudotool anyway by now23:12
inc0I'd rather have some simple playbook to take existing configs/password.yaml and output dir with rendered kube resources23:13
inc0then you just kubectl whole dir23:13
sdakeinc0 as long as you aren't married to the code inc0 - as when we move to helm its going byebye :)23:13
inc0it's going to be single file ansible play23:14
inc0no, I'll get rid of it happily23:14
sdakecool23:14
inc0at least that will allow us to kickstart work easily and do one config at the time23:14
kfox1111we need it for just a little bit of ceph, and the openvswitch-set-ip thingy.23:14
kfox1111too.23:14
inc0yeah, I have local cephy thing too23:15
kfox1111those should be moved to helm for sure though. shouldn't be much work left.23:15
inc0I'll publish it with same idea23:15
kfox1111ceph's half way over already.23:15
inc0what I'm afraid of is lack of overrides23:15
sdakeoverrides are manageable directly in the openstack services23:15
inc0it's gonna to be bitch to arrive to our merge_config feature parity23:15
sdakeinc0 i ahd same question of kfox111123:16
*** mpansky has quit IRC23:16
sdakeinc0 read this log:23:16
kfox1111is merge_config seperable from kolla-ansible?23:17
kfox1111or is it ansible code?23:17
inc0kfox1111: it's ansible module23:18
inc0I mean we can rewrite it23:18
inc0but doesn't make sense23:18
inc0imho23:18
kfox1111it could be used as an init container.23:18
inc0as tbh kolla-ansible genconfig just works23:18
inc0right...well23:18
inc0it's going to be harder as per-node override23:19
kfox1111why?23:19
inc0ansible already gives us infrastructure to define it by hostname and such23:20
sdakewell i can't find the log at this moment23:20
inc0ofc, doable23:20
sdakehowever- the idea is to run nova config1 config2 config323:20
sdakethat permits config overrides23:20
inc0yeah we discussed that in pth23:20
sdakeinc0 we were unable to determine why we didn't use this in kolla-ansible23:20
inc0ptg23:20
sdakeit was also discussed on irc recently23:20
inc0because oslo.config started to support it relatively lately23:21
sdakethe exchange on irc indicated its been a feature since essex.23:21
inc0by the time we wrote merge_config that wasn't the case23:21
inc0well23:21
inc0then I'm mistaken23:21
inc0anyway23:21
sdakei htink the reasosn we didn't use it is we didn't know about it as a feature23:21
inc0possible23:21
sdakeper node custom configs is easy in this model23:22
kfox1111inc0: its supported it for many years.23:22
sdakeI believe all the use cases are covered23:22
inc0ok then, we just need to write the thing23:23
kfox1111yup.23:23
sdakething being helm external config maps?23:23
inc0in the meantime I'll crack my quick playbook to get us rolling23:23
mnaserhttps://review.openstack.org/#/c/447713/ this merged23:27
mnaserso i think recheck23:27
mnasershould clear the gate up23:27
kfox1111still think we shouldn't spend muhc time writing code that we shoudl get rid of asap.23:27
kfox1111but, whatever.23:28
kfox1111the problem isn't pip install kolla-kubernetes is hard. its that all pip/genconfig's a pain.23:28
portdirectsdake: ping23:29
sdakeportdirect shoot23:29
sdakemnaser yup a recheck will do the job - no need to rebase23:30
mnaserdonezo, hopefully it flows through23:30
inc0kfox1111: yes and no - if it takes few hrs to automate this thing, I'll just do it23:30
portdirectsdake: just replying to your ping, sup dude?23:30
*** eaguilar has joined #openstack-kolla23:31
sdakeportdirect oh - v1k0d3n indicated i should communicate with his team via PR's, so I've done that - however, here is the PR: https://github.com/att-comdev/halcyon-kubernetes/pull/5623:31
kfox1111inc0: plus more to redo the docs23:32
inc0kfox1111: what docs?:P23:32
kfox1111inc0: the docs people keep writing. ;)23:32
inc0also, that will need redoing anyway23:32
*** masber has quit IRC23:32
inc0so it's a quck fix to what I consider broken today23:32
*** rhallisey has joined #openstack-kolla23:32
inc0keyword is quick23:32
v1k0d3nsdake done/merged23:33
sdakethanks v1k0d3n23:33
v1k0d3nthe image was created earlier today already.23:33
sdakev1k0d3n cool thanks :)23:33
v1k0d3nanytime23:33
kfox1111replacing python with ansible just doesn't seem to be a step in the right direction to me. but again, whatever.23:34
sdakekfox1111 agreed - we will just delete the ansible but inc0 said he wasn't married to it, so if inc0 wants to waste his time more power to him :)23:34
portdirectNot sure I follow but long as you guys are good.23:35
sbezverkgents kfox1111 and myself just brought up a baremetal VM  using ironic running on kolla kubernetes23:35
sbezverkthat was fraking awesome!!!23:35
sdakeportdirect http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2017-03-20.log.html#t2017-03-20T17:46:2123:35
sbezverkfreaking I meant23:35
portdirectsbezverk: you got time this week to chat?23:35
sdakeportdirect for more context23:35
sbezverkportdirect: absolutely23:35
spsuryamorning all23:36
*** vhosakot has joined #openstack-kolla23:36
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: Fernet Token Support  https://review.openstack.org/44627423:38
sdakesup spsurya23:38
portdirectsbezverk: nice one, think wed is good for me? I can hit up srwilkers and check with him.23:38
sdakesbezverk rockin dude, was it baremetal in the gate?23:39
sbezverkportdirect: wednesday work for me too, prefer am if it s possible23:39
sbezverksdake: not at the gate yet, to resolv connectivity issues I had to build it locally to debug23:40
sdakesbezverk ya its pretty sweet to see that first bare metal node boot up in ironic :)23:40
sbezverksdake: especially ALL is running ont the single physcial server ;)23:41
*** dave-mccowan has joined #openstack-kolla23:44
*** manheim has quit IRC23:44
sdakesbezverk could you expand - i'm not sure I follow how you run kubernetes on the same server as the baremetal node that ironic boots23:45
*** vhosakot has quit IRC23:45
kfox1111sdake: baremetal vm.23:45
kfox1111simulated baremetal.23:46
sdakekfox1111 got it thanks :)23:46
kfox1111:)23:46
*** vhosakot has joined #openstack-kolla23:46
sdakevhosakot this needs an ack: https://review.openstack.org/#/c/447217/23:48
vhosakotsdake: done, although the ubuntu source xenial gate has an unrelated http://logs.openstack.org/17/447217/2/check/gate-kolla-dsvm-deploy-ubuntu-source-ubuntu-xenial-nv/40fa69b/console.html#_2017-03-18_15_17_35_503927.23:50
sdakevhosakot yup iiuc that has been broken for ages23:50
vhosakotyep, I have seen that zuul error before.23:51
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: Update to 1.5.4 in development environment documentation  https://review.openstack.org/44773123:52
inc0kfox1111 sbezverk can I get kubectl get configmap mariadb -o yaml please?23:53
inc0to confirm structure I'm generating23:53
kfox1111inc0: config's are here: http://logs.openstack.org/74/446274/10/check/gate-kolla-kubernetes-deploy-centos-binary-2-external-ovs-nv/a7858c7/logs/configmaps.yaml23:56
inc0thank you good sir23:57
kfox1111almost there... just gotta fix rotate now...23:59

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