openstackgerrit | Wei Cao proposed openstack/kolla: Remove Fedora support from manilla-data https://review.openstack.org/394074 | 00:00 |
---|---|---|
*** sdake has joined #openstack-kolla | 00:13 | |
*** portdirect has quit IRC | 00:16 | |
*** absubram has quit IRC | 00:18 | |
*** portdirect has joined #openstack-kolla | 00:19 | |
*** DTadrzak has quit IRC | 00:19 | |
*** david-lyle has quit IRC | 00:20 | |
*** yingjun has joined #openstack-kolla | 00:25 | |
*** neilus has joined #openstack-kolla | 00:25 | |
*** neilus has quit IRC | 00:30 | |
*** schwicht has joined #openstack-kolla | 00:30 | |
openstackgerrit | Wei Cao proposed openstack/kolla: Add karbor container https://review.openstack.org/395006 | 00:31 |
Pavo | anyone around/ | 00:31 |
*** schwicht has quit IRC | 00:34 | |
openstackgerrit | Joshua Harlow proposed openstack/kolla: Show the rendered docker file https://review.openstack.org/395272 | 00:35 |
*** srwilkers has joined #openstack-kolla | 00:37 | |
sdake | sup pavo | 00:38 |
Pavo | I was gonna ask about tls deployment think I figured it out | 00:38 |
Pavo | if you are using a secure docker registry does the bootstrap-servers copy over the certs? | 00:40 |
*** chas_ has joined #openstack-kolla | 00:44 | |
openstackgerrit | Joshua Harlow proposed openstack/kolla: Add ability to save the things built https://review.openstack.org/395273 | 00:45 |
openstackgerrit | Joshua Harlow proposed openstack/kolla: Add ability to save the things built https://review.openstack.org/395273 | 00:46 |
openstackgerrit | Joshua Harlow proposed openstack/kolla: Add ability to save the things built https://review.openstack.org/395273 | 00:47 |
*** chas_ has quit IRC | 00:49 | |
*** tovin07 has quit IRC | 00:49 | |
*** hieulq has quit IRC | 00:49 | |
*** hieulq has joined #openstack-kolla | 00:52 | |
*** diogogmt has quit IRC | 00:52 | |
*** tovin07 has joined #openstack-kolla | 00:54 | |
*** zhubingbing has joined #openstack-kolla | 01:19 | |
openstackgerrit | Wei Cao proposed openstack/kolla: Add karbor container https://review.openstack.org/395006 | 01:19 |
*** neilus has joined #openstack-kolla | 01:21 | |
openstackgerrit | zhubingbing proposed openstack/kolla: add panko dockerfile https://review.openstack.org/387232 | 01:24 |
*** neilus has quit IRC | 01:25 | |
*** zhurong has joined #openstack-kolla | 01:30 | |
*** sdake has quit IRC | 01:37 | |
*** diogogmt has joined #openstack-kolla | 01:39 | |
*** chas_ has joined #openstack-kolla | 01:45 | |
*** chas_ has quit IRC | 01:49 | |
*** duonghq has joined #openstack-kolla | 01:50 | |
duonghq | morning | 01:50 |
duonghq | coolsvap, are you free right now? | 01:53 |
*** ayoung has quit IRC | 01:54 | |
*** schwicht has joined #openstack-kolla | 01:58 | |
harlowja | anyone have an example of using https://github.com/openstack/kolla/blob/master/kolla/template/filters.py#L19 | 02:05 |
harlowja | do i just set some override in my jinja2 header? | 02:05 |
*** tovin07_ has joined #openstack-kolla | 02:06 | |
harlowja | nm, i see http://docs.openstack.org/developer/kolla/image-building.html#package-customisation | 02:06 |
*** unicell has quit IRC | 02:08 | |
*** neilus has joined #openstack-kolla | 02:17 | |
*** david-lyle has joined #openstack-kolla | 02:20 | |
*** david-lyle has quit IRC | 02:20 | |
*** neilus has quit IRC | 02:21 | |
*** david-lyle has joined #openstack-kolla | 02:22 | |
zhubingbing | ping Mauricio Lima | 02:34 |
*** chas_ has joined #openstack-kolla | 02:45 | |
*** chas_ has quit IRC | 02:50 | |
*** srwilkers has quit IRC | 03:06 | |
*** zhubingbing has quit IRC | 03:14 | |
*** zhubingbing has joined #openstack-kolla | 03:17 | |
*** haplo37 has quit IRC | 03:22 | |
*** haplo37 has joined #openstack-kolla | 03:30 | |
*** dave-mccowan has quit IRC | 03:38 | |
*** portdirect has quit IRC | 03:44 | |
*** chas_ has joined #openstack-kolla | 03:46 | |
*** chas_ has quit IRC | 03:51 | |
openstackgerrit | Joshua Harlow proposed openstack/kolla: Add ability to save the things built https://review.openstack.org/395273 | 03:51 |
*** schwicht has quit IRC | 04:10 | |
*** fragatin_ has joined #openstack-kolla | 04:26 | |
*** fragatina has quit IRC | 04:29 | |
*** fragatin_ has quit IRC | 04:31 | |
duonghq | anybody build image recently with base: centos:7; as I can see, there is no openvswitch in epel | 04:44 |
openstackgerrit | Joshua Harlow proposed openstack/kolla: Stop matching incorrect plugin prefixes https://review.openstack.org/395399 | 05:00 |
*** fragatina has joined #openstack-kolla | 05:03 | |
*** fragatina has quit IRC | 05:08 | |
*** saneax-_-|AFK is now known as saneax | 05:16 | |
*** david-lyle has quit IRC | 05:22 | |
*** fragatina has joined #openstack-kolla | 05:22 | |
*** david-lyle has joined #openstack-kolla | 05:23 | |
*** fragatina has quit IRC | 05:27 | |
*** chas_ has joined #openstack-kolla | 05:48 | |
*** chas_ has quit IRC | 05:52 | |
*** haplo37_ has quit IRC | 06:06 | |
*** g3ek has quit IRC | 06:13 | |
*** haplo37 has quit IRC | 06:13 | |
*** haplo37 has joined #openstack-kolla | 06:23 | |
*** haplo37_ has joined #openstack-kolla | 06:25 | |
*** g3ek has joined #openstack-kolla | 06:26 | |
*** zhurong has quit IRC | 06:35 | |
*** zhurong has joined #openstack-kolla | 06:37 | |
*** nihilifer has joined #openstack-kolla | 06:40 | |
*** chas_ has joined #openstack-kolla | 06:48 | |
*** jtriley has joined #openstack-kolla | 06:51 | |
*** chas_ has quit IRC | 06:53 | |
*** msimonin has joined #openstack-kolla | 06:54 | |
zhubingbing | hi guys | 06:56 |
sp_ | zhubingbing: hi | 06:56 |
zhubingbing | hi | 06:56 |
*** jtriley has quit IRC | 06:56 | |
zhubingbing | nice meet you | 06:56 |
sp_ | nice to meet you too | 06:57 |
sp_ | zhubingbing: do you have something to ask ?? though i am new | 06:58 |
zhubingbing | np | 06:59 |
zhubingbing | no question | 06:59 |
*** unicell has joined #openstack-kolla | 07:08 | |
*** Jeffrey4l has joined #openstack-kolla | 07:09 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: Fix plugin parsing for base images https://review.openstack.org/394267 | 07:18 |
*** chas_ has joined #openstack-kolla | 07:19 | |
saneax | Hi folks | 07:25 |
saneax | was looking to install and try kolla-kubernetes, and following the docs here - http://docs.openstack.org/developer/kolla-kubernetes/index.html | 07:29 |
saneax | is there a separate IRC for kolla-kubernetes? | 07:29 |
jascott1 | no | 07:30 |
jascott1 | (not that they have told me about :) | 07:30 |
jascott1 | saneax did you have a question bout kolla-k8s? | 07:33 |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch https://review.openstack.org/393877 | 07:33 |
saneax | jascott1, yes, thanks - I have a baremetal with 64G and 24 Cores - thinking can I create 2 to 3 nodes with KVM and install a multinode setup? | 07:34 |
jascott1 | sounds reasonable | 07:35 |
saneax | also, I have no previous exposure to installing kolla | 07:35 |
saneax | so, I am skipping the kolla installation and folling the kolla-k8s quickstart | 07:35 |
saneax | unforunate the doc on the quickstart does not talk of multinode setup | 07:36 |
saneax | it seems like its a single node install? | 07:36 |
jascott1 | i would look at all the docs not just the quickstart | 07:37 |
jascott1 | also there is a multinode doc | 07:37 |
jascott1 | http://docs.openstack.org/developer/kolla-kubernetes/multi-node.html | 07:37 |
sp_ | jascott1: is it possible to deploy kolla-k8s on single node ?? | 07:38 |
saneax | Ok jascott1 | 07:39 |
jascott1 | sp_ yes | 07:40 |
jascott1 | i would check this http://docs.openstack.org/developer/kolla-kubernetes/index.html | 07:40 |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch https://review.openstack.org/393877 | 07:40 |
saneax | thanks jascott1 | 07:41 |
sp_ | thanks *jascott1* | 07:43 |
jascott1 | np | 07:43 |
*** zhubingbing has quit IRC | 07:43 | |
*** msimonin has quit IRC | 07:47 | |
*** neilus has joined #openstack-kolla | 07:47 | |
*** zhubingbing has joined #openstack-kolla | 07:47 | |
*** jtriley has joined #openstack-kolla | 07:51 | |
*** neilus has quit IRC | 07:52 | |
*** matrohon has joined #openstack-kolla | 07:53 | |
*** jtriley has quit IRC | 07:57 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch https://review.openstack.org/393877 | 08:01 |
*** zhubingbing has quit IRC | 08:02 | |
*** dcwangmit01_ has joined #openstack-kolla | 08:03 | |
*** dcwangmit01 has quit IRC | 08:05 | |
*** caowei_ has joined #openstack-kolla | 08:08 | |
*** shardy has joined #openstack-kolla | 08:09 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch https://review.openstack.org/393877 | 08:09 |
*** b_bezak has joined #openstack-kolla | 08:10 | |
*** rmart04 has joined #openstack-kolla | 08:16 | |
*** b_bezak_ has joined #openstack-kolla | 08:17 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch https://review.openstack.org/393877 | 08:17 |
*** b_bezak has quit IRC | 08:20 | |
*** b_bezak has joined #openstack-kolla | 08:21 | |
*** b_bezak_ has quit IRC | 08:24 | |
*** f13o has joined #openstack-kolla | 08:29 | |
*** b_bezak has quit IRC | 08:31 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: Use openstack_service_workers variable in gate https://review.openstack.org/394148 | 08:43 |
*** caowei_ has quit IRC | 08:47 | |
*** openstackgerrit has quit IRC | 08:48 | |
*** openstackgerrit has joined #openstack-kolla | 08:48 | |
*** jtriley has joined #openstack-kolla | 08:53 | |
*** gfidente has joined #openstack-kolla | 08:53 | |
*** bjolo has joined #openstack-kolla | 08:53 | |
bjolo | morning | 08:53 |
duonghq | ping bjolo | 08:54 |
bjolo | duonghq, sup | 08:55 |
duonghq | saneax, some more info: I can run 2 node deployment w/ KVM on machine w/ 16GB RAM :) | 08:55 |
duonghq | bjolo, did you build image recently with centos:7 base/ | 08:55 |
bjolo | yes | 08:56 |
bjolo | 2 days ago | 08:56 |
duonghq | did you have trouble with openvswitch? | 08:56 |
bjolo | nope | 08:56 |
bjolo | not that i know of | 08:56 |
duonghq | I cannot get openvswitch installed | 08:56 |
bjolo | ok | 08:56 |
duonghq | it's not in epel7 repo | 08:56 |
bjolo | let me kick of a build | 08:56 |
bjolo | epel repo | 08:57 |
bjolo | is that used by default or something that you have added? | 08:58 |
*** jtriley has quit IRC | 08:58 | |
duonghq | it's from epel-release which in turn is install by default, | 08:58 |
duonghq | correct me if I wrong | 08:58 |
*** jrist has quit IRC | 08:59 | |
openstackgerrit | Wei Cao proposed openstack/kolla: [WIP] Add karbor ansible role https://review.openstack.org/395022 | 08:59 |
*** Pavo has quit IRC | 09:00 | |
*** jrist has joined #openstack-kolla | 09:00 | |
*** caowei_ has joined #openstack-kolla | 09:02 | |
openstackgerrit | Wei Cao proposed openstack/kolla: Add karbor container https://review.openstack.org/395006 | 09:03 |
*** Serlex has joined #openstack-kolla | 09:09 | |
*** egonzalez90 has joined #openstack-kolla | 09:10 | |
*** sdake has joined #openstack-kolla | 09:11 | |
sdake | hey peeps | 09:11 |
*** stvnoyes1 has joined #openstack-kolla | 09:19 | |
*** stvnoyes has quit IRC | 09:19 | |
*** neilus has joined #openstack-kolla | 09:26 | |
*** neilus_ has joined #openstack-kolla | 09:30 | |
*** msimonin has joined #openstack-kolla | 09:30 | |
duonghq | hi sdake | 09:30 |
*** zhurong has quit IRC | 09:32 | |
*** neilus has quit IRC | 09:32 | |
duonghq | bjolo, do you got any trouble with openvswitch? | 09:33 |
bjolo | centos binary built just fine | 09:34 |
*** zhurong has joined #openstack-kolla | 09:35 | |
bjolo | could be the mirror that you are using that has issues | 09:35 |
*** caowei_ has quit IRC | 09:35 | |
bjolo | or the great fw of china | 09:35 |
*** msimonin has quit IRC | 09:35 | |
bjolo | hi sdake | 09:35 |
*** msimonin has joined #openstack-kolla | 09:36 | |
sdake | sup bjolo | 09:38 |
*** sdake has quit IRC | 09:38 | |
bjolo | up late | 09:38 |
duonghq | bjolo, I'm in Vietnam | 09:40 |
bjolo | duonghq, ok sorry thougth you were in china :) | 09:41 |
duonghq | bjolo, which repo does this package come from? | 09:41 |
bjolo | hmm how do i check that_ | 09:41 |
bjolo | ? | 09:41 |
duonghq | you can start any container and jump in, run yum info openvswitch | 09:42 |
bjolo | true :) | 09:42 |
*** yingjun has quit IRC | 09:42 | |
openstackgerrit | zhubingbing proposed openstack/kolla: add panko dockerfile https://review.openstack.org/387232 | 09:42 |
*** zhubingbing has joined #openstack-kolla | 09:45 | |
*** rmart04 has quit IRC | 09:45 | |
*** egonzalez has joined #openstack-kolla | 09:48 | |
*** egonzalez90 has quit IRC | 09:48 | |
duonghq | egonzalez, ping | 09:48 |
egonzalez | duonghq, pong | 09:49 |
openstackgerrit | Manikandan R proposed openstack/kolla: Corrects typo "requried" in kolla_docker.py https://review.openstack.org/395492 | 09:49 |
duonghq | how do you think about my policy patch, | 09:49 |
duonghq | I should remove non-API service you commented | 09:49 |
duonghq | or fix it in follow-up patch? | 09:49 |
duonghq | I'm not sure | 09:49 |
egonzalez | I think the best option is keep all services for now. At least until we are sure which one need only API and which not. | 09:50 |
*** b_bezak has joined #openstack-kolla | 09:51 | |
egonzalez | Any other voice on this? Thanks | 09:51 |
egonzalez | Can you share the PS link? | 09:51 |
duonghq | egonzalez, moment | 09:52 |
bjolo | morning egonzalez | 09:52 |
duonghq | #link https://review.openstack.org/#/c/394260/ | 09:52 |
duonghq | thank egonzalez | 09:53 |
bjolo | looking at your comments on this https://review.openstack.org/#/c/392094/5/ansible/group_vars/all.yml | 09:53 |
bjolo | https://review.openstack.org/#/c/392094/5 | 09:53 |
egonzalez | Ia not wrong, commented after that | 09:53 |
*** jtriley has joined #openstack-kolla | 09:54 | |
bjolo | are you ok with +2 on this one now? looks good to me. The all.yml tunnel_interface_address will be set for each host correctly | 09:54 |
egonzalez | I think someone from Kubernetes need to validate | 09:54 |
egonzalez | Because that variable was introduced by them | 09:55 |
bjolo | ok a few different things here | 09:55 |
bjolo | kolla-ansible needs to fix this as well | 09:55 |
bjolo | are you saying that the code in all.yml would not work? | 09:56 |
*** neilus_ has quit IRC | 09:56 | |
egonzalez | Will work for Ansible but don't know if for Kubernetes will do | 09:56 |
bjolo | kube people can fix it in their repo ;) | 09:57 |
bjolo | sdake around? | 09:58 |
*** jtriley has quit IRC | 09:59 | |
saneax | thanks duonghq | 10:01 |
saneax | I am trying out and will let you folks know how it goes | 10:01 |
*** zhurong has quit IRC | 10:01 | |
egonzalez | bjolo, were you able to make networking work? | 10:02 |
bjolo | nope | 10:02 |
bjolo | not yet | 10:03 |
bjolo | im backtracking and just did a minimal deploy | 10:03 |
bjolo | did a git pull just to learn that latest PS for kibana to fix logpath is broken :( | 10:03 |
bjolo | no central logging atm | 10:03 |
bjolo | we really need better gates | 10:04 |
egonzalez | Welcome to the tcpdump around the 1000 devices neutron creates ;) | 10:04 |
bjolo | haha i know | 10:04 |
bjolo | neutron is horrible | 10:04 |
*** zhubingbing has quit IRC | 10:05 | |
bjolo | this is a really good walkthrough https://www.youtube.com/watch?v=7IXEtUEZslg | 10:05 |
egonzalez | Is funny when fails in PoC | 10:05 |
egonzalez | When fails on prod. Look for another company | 10:05 |
bjolo | haha | 10:05 |
*** zhubingbing has joined #openstack-kolla | 10:06 | |
bjolo | i went beta testing friday | 10:06 |
bjolo | swear to god we tested networking, but in beta did not | 10:06 |
bjolo | now everyone is chasing me to get it fixed | 10:06 |
bjolo | and im just hitting the fricking wall on this one | 10:06 |
bjolo | so the fact that kibana is not working is kinda frustrating | 10:08 |
bjolo | we really need better testing | 10:08 |
bjolo | and i mean large, all services enabled, integration testing. | 10:09 |
bjolo | with TLS | 10:09 |
bjolo | multinode | 10:09 |
bjolo | multinetwork | 10:09 |
bjolo | deploy, tempest run; change config; upgrade; tempest run | 10:10 |
*** tovin07_ has quit IRC | 10:10 | |
bjolo | as the number of openstack project are added to kolla, this just gets more and more critical | 10:10 |
*** neilus has joined #openstack-kolla | 10:10 | |
bjolo | i fear we will implode and drown in "this is not working bugs" | 10:11 |
egonzalez | Totally agree | 10:14 |
egonzalez | Can you gather some info from your nodes, i will try to debug dvr at the evening | 10:14 |
egonzalez | Namespaces present in neutron and compute nodes, also docker containers running on them | 10:15 |
openstackgerrit | zhubingbing proposed openstack/kolla: add panko dockerfile https://review.openstack.org/387232 | 10:15 |
*** DTadrzak has joined #openstack-kolla | 10:15 | |
egonzalez | And ovs vsctl-show in neutron ovs containers | 10:16 |
bjolo | duonghq, epel: mirrors.telianet.dk | 10:17 |
bjolo | yum info openvswitch | 10:17 |
duonghq | thank bjolo | 10:17 |
bjolo | fresh build right now | 10:18 |
bjolo | so it should be good | 10:18 |
duonghq | cannot understand why I cannot install openvswitch | 10:18 |
bjolo | whats you build setup? | 10:18 |
duonghq | as default, and centos/source | 10:19 |
bjolo | whats you build command? | 10:19 |
duonghq | I use build in tool | 10:19 |
bjolo | me too | 10:20 |
duonghq | ./build.py -i .header .I .footer openvswitch-base | 10:20 |
bjolo | and whats in header and footer? | 10:20 |
duonghq | proxy | 10:21 |
bjolo | i would add --nocache | 10:21 |
duonghq | me too | 10:21 |
bjolo | whats the output from docker images? | 10:21 |
bjolo | sometimes you can get weird stuff from docker | 10:21 |
bjolo | docker images -q | xargs -I {} docker rmi -f {} | 10:22 |
bjolo | cleans them all out | 10:22 |
*** neilus has quit IRC | 10:22 | |
duonghq | it said that cannot found openvswitch | 10:22 |
duonghq | it's happen even when I jump in centos:7 and run openvswitch | 10:23 |
duonghq | yum -y install openvswitch | 10:23 |
*** neilus has joined #openstack-kolla | 10:23 | |
bjolo | yum update first | 10:24 |
bjolo | yum repolist | 10:24 |
bjolo | yum search openvswitch | 10:24 |
duonghq | moment | 10:25 |
bjolo | duonghq, remove containers as well before removing images | 10:28 |
duonghq | sure | 10:29 |
*** zhubingbing has quit IRC | 10:29 | |
duonghq | but I think the default repo of Kolla should be update | 10:29 |
duonghq | it Dockerfile | 10:29 |
duonghq | *in | 10:29 |
bjolo | isnt epel a dynamic repo? | 10:31 |
duonghq | sure | 10:31 |
bjolo | i.e. it tries out several ones to find the best one for your location | 10:31 |
duonghq | bjolo, I create epel mirror locally | 10:31 |
*** tonanhngo has quit IRC | 10:31 | |
bjolo | ok | 10:31 |
bjolo | is the package there? | 10:32 |
bjolo | what tool did you use to mirror the repo? | 10:32 |
duonghq | no luck | 10:32 |
duonghq | I used reposync | 10:33 |
duonghq | official tool of yum | 10:33 |
duonghq | from yum-utils | 10:33 |
bjolo | any errors or issues? | 10:34 |
egonzalez | May be the problem the openvswitch base is build from base instead of openstack-base | 10:34 |
duonghq | no, everything just fine | 10:34 |
duonghq | egonzalez, openvswitch is installed in openvswitch-base | 10:34 |
bjolo | is the openvswitch package in your local repo? | 10:34 |
duonghq | bjolo, no | 10:34 |
bjolo | then thats your issue right | 10:34 |
bjolo | not the kolla build | 10:35 |
duonghq | bjolo, https://n40lab.wordpress.com/2016/03/02/openvswitch-lts-in-centos-7/ | 10:35 |
duonghq | bjolo, yup | 10:35 |
duonghq | the openvswitch issue | 10:35 |
duonghq | repo issue | 10:35 |
bjolo | hmm so how come it works for me? | 10:36 |
bjolo | no issues what so ever | 10:36 |
duonghq | I got this error just from this week | 10:37 |
bjolo | i dont have any local repos or build template overrides | 10:37 |
duonghq | I cannot understand where is my setup grab openvswitch till now | 10:38 |
duonghq | centos 6 is ok | 10:38 |
*** neilus has quit IRC | 10:38 | |
bjolo | ./build.py --config-file /etc/kolla/kolla-build.conf --registry dockreg.mydomain.net:4000 --namespace $NAMESPACE --push --nocache --base centos --type binary --tag $TAG --logs-dir $LOGS | 10:39 |
bjolo | the essential part in my build script | 10:39 |
duonghq | I just put your option in kolla-build file | 10:39 |
duonghq | your 's same as me basically | 10:39 |
bjolo | in my script i build for centos source/binary and ubuntu source/binary | 10:40 |
bjolo | hence the long command line :) | 10:40 |
duonghq | it's ok, just personal taste | 10:41 |
openstackgerrit | Wei Cao proposed openstack/kolla: Add karbor container https://review.openstack.org/395006 | 10:43 |
duonghq | bjolo, I go home right now | 10:43 |
duonghq | see you in the meeting | 10:43 |
*** duonghq has quit IRC | 10:43 | |
bjolo | ok | 10:47 |
*** ppalacios has joined #openstack-kolla | 10:54 | |
*** jtriley has joined #openstack-kolla | 10:55 | |
*** msimonin has quit IRC | 10:57 | |
*** msimonin has joined #openstack-kolla | 10:59 | |
*** jtriley has quit IRC | 11:00 | |
*** neilus has joined #openstack-kolla | 11:01 | |
*** DanyC has joined #openstack-kolla | 11:02 | |
openstackgerrit | Surya Prakash Singh proposed openstack/kolla: Consistent home directory creation for all the services https://review.openstack.org/390179 | 11:06 |
*** msimonin has quit IRC | 11:08 | |
*** neilus has quit IRC | 11:13 | |
*** schwicht has joined #openstack-kolla | 11:23 | |
*** saneax is now known as saneax-_-|AFK | 11:28 | |
*** caowei_ has joined #openstack-kolla | 11:29 | |
*** neilus has joined #openstack-kolla | 11:32 | |
openstackgerrit | Surya Prakash Singh proposed openstack/kolla: Consistent home directory creation for all the services https://review.openstack.org/390179 | 11:33 |
*** portdirect has joined #openstack-kolla | 11:37 | |
*** tonanhngo has joined #openstack-kolla | 11:38 | |
*** tonanhngo has quit IRC | 11:40 | |
*** mliima has joined #openstack-kolla | 11:41 | |
*** neilus has quit IRC | 11:42 | |
*** egonzalez90 has joined #openstack-kolla | 11:48 | |
*** egonzalez has quit IRC | 11:48 | |
*** DTadrzak has quit IRC | 11:52 | |
*** caowei_ has quit IRC | 11:54 | |
*** jtriley has joined #openstack-kolla | 11:55 | |
*** jtriley has quit IRC | 12:01 | |
*** jmccarthy has quit IRC | 12:02 | |
*** jmccarthy has joined #openstack-kolla | 12:03 | |
*** neilus has joined #openstack-kolla | 12:04 | |
*** DanyC has left #openstack-kolla | 12:10 | |
*** caowei has joined #openstack-kolla | 12:12 | |
*** DTadrzak has joined #openstack-kolla | 12:14 | |
*** mkoderer has joined #openstack-kolla | 12:26 | |
*** msimonin has joined #openstack-kolla | 12:27 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch https://review.openstack.org/393877 | 12:32 |
*** schwicht has quit IRC | 12:33 | |
*** caowei has quit IRC | 12:33 | |
bjolo | egonzalez90, i think i have found something. mtu size on br-tun | 12:38 |
egonzalez90 | Interesting, what mtu size you had? | 12:39 |
bjolo | i have set mtu 9000 in neutron | 12:40 |
pomac | All interfaces except some have 9000 - the problem is that some has 1500 | 12:40 |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch https://review.openstack.org/393877 | 12:40 |
bjolo | but br-tun is still 1500 | 12:40 |
pomac | bjolo: sorry =) | 12:40 |
*** DTadrzak has quit IRC | 12:40 | |
bjolo | br-tun is vxlan over UDP and UDP does not fragment right? | 12:41 |
bjolo | hi pomac | 12:41 |
bjolo | (colleague of mine) | 12:41 |
pomac | bjolo: UDP does not fragment unless done manually | 12:41 |
*** tyrola has joined #openstack-kolla | 12:42 | |
*** DTadrzak has joined #openstack-kolla | 12:42 | |
bjolo | i cant find anywhere in kolla where i can change/set br-tun mtu | 12:43 |
* bjolo is investigating | 12:43 | |
egonzalez90 | IIRC we only configure MTU at instances(dhcp agent) | 12:44 |
egonzalez90 | Nothing on the baremetal side | 12:44 |
tyrola | Hey guys. Can anyone help me with my kolla issue? I am trying to setup kolla with tagged vlans for api_interface | 12:45 |
bjolo | tyrola, create a vlan interface on the host side | 12:45 |
tyrola | yes I did. My network interface is called just "network". I've added network.140 (for vlan id 140) | 12:46 |
tyrola | after setting it to api_interface: "network.140" it creates some errors while deploying | 12:46 |
tyrola | fatal: [controller01] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'ipv4'", 'failed': True} | 12:46 |
tyrola | But this interface has a valid ipv4. | 12:46 |
bjolo | what does prechecks say? | 12:47 |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: Fix horizon dashboard plugin https://review.openstack.org/393898 | 12:47 |
bjolo | there is an issue that rabbitmq requires name resolution and it does that on network_interface | 12:48 |
bjolo | but it requires that hostname should be resolved to IP on api_interface | 12:48 |
*** sdake has joined #openstack-kolla | 12:48 | |
bjolo | there is a bugg on this | 12:48 |
*** nradojevic has joined #openstack-kolla | 12:48 | |
bjolo | i my setup i dont use a dedicated api_interface | 12:48 |
bjolo | treat network_interface as api interface | 12:48 |
*** zhurong has joined #openstack-kolla | 12:49 | |
*** zhubingbing has joined #openstack-kolla | 12:50 | |
bjolo | Jeffrey4l, nice PS :) | 12:52 |
*** caowei_ has joined #openstack-kolla | 12:52 | |
bjolo | please tell me we get this backported to newton :) | 12:52 |
nradojevic | Hi, I've deleted the neutron-server container on my controller hosts and tried to deploy them again. But now I'm getting the following error message: chmod: changing permissions of '/var/log/kolla/neutron': Operation not permitted | 12:52 |
nradojevic | Can someone help me to solve this? I'm using stable/mitaka release. | 12:52 |
Jeffrey4l | bjolo, dashboard? yep, i think it can be backport to newton ;) | 12:53 |
bjolo | yes | 12:53 |
tyrola | prechecks is failing at: Checking if kolla_internal_vip_address is in the same network as network_interface on all nodes | 12:55 |
bjolo | tyrola, ok | 12:55 |
bjolo | hmm did not know that was actually a requirement | 12:55 |
bjolo | i have that i my setup, but unknowingly | 12:56 |
bjolo | egonzalez90, there are quite a few config (kolla config overide) options for neutron and MTU | 12:57 |
*** jtriley has joined #openstack-kolla | 12:57 | |
*** caowei_ has quit IRC | 12:57 | |
bjolo | tyrola, what distro is on your hosts? | 12:58 |
tyrola | cent os 7 | 12:58 |
tyrola | and the containers too | 12:59 |
bjolo | hmm can you really have a network interface named "network" | 12:59 |
bjolo | thought there were some form of naming standard for this | 12:59 |
pomac | not really | 12:59 |
pomac | ask systemd ppl - ;) | 12:59 |
portdirect | you can name them whatever you like | 13:00 |
*** msimonin has quit IRC | 13:00 | |
tyrola | it has been renamed in persistent rules 70 :) | 13:00 |
tyrola | I have 2 interfaces named network and storage | 13:01 |
bjolo | yes, thats one thing, but if you want all the tools/scripts that handles networking to work properly i dont think you can. I have read some where the docs dictating allowed names on interfaces | 13:01 |
*** zhurong has quit IRC | 13:01 | |
*** jtriley has quit IRC | 13:02 | |
*** dwalsh has joined #openstack-kolla | 13:02 | |
pomac | sure, there can be things that expect network as a parameter/argument | 13:02 |
tyrola | Oh I think I know what you mean. Ansible generated a variable ansible_<network interface name> and maybe this variables "ansible_network" is being used already | 13:03 |
bjolo | tyrola, yes things like that | 13:03 |
bjolo | for ex | 13:03 |
tyrola | so it can't detect anssible_network.ipv4 | 13:03 |
tyrola | I will rename the interfaces on all nodes, give me some minutes | 13:03 |
*** portdirect has quit IRC | 13:04 | |
tyrola | Do you know where I can find the rules of allowed names? Would be great if I can see by the name if it's storage or network. | 13:04 |
*** jtriley has joined #openstack-kolla | 13:06 | |
*** zhurong has joined #openstack-kolla | 13:06 | |
openstackgerrit | Wang Liming proposed openstack/kolla: source doc bifrost.rst charactor error https://review.openstack.org/395581 | 13:08 |
*** mgiles has joined #openstack-kolla | 13:09 | |
*** jtriley has quit IRC | 13:10 | |
*** neilus has quit IRC | 13:10 | |
*** lamt has joined #openstack-kolla | 13:10 | |
tyrola | Ok seems like Ansible has a problem if the network interface contains a . (dot) for vlan tags. | 13:15 |
tyrola | the interface is now called "ifnetwork.140". And Ansible thinks .140 is a attribute. | 13:16 |
tyrola | One or more undefined variables: 'dict object' has no attribute u'ansible_ifnetwork.140'", 'failed': True} | 13:16 |
openstackgerrit | Wang Liming proposed openstack/kolla: source doc bifrost.rst charactor error https://review.openstack.org/395586 | 13:16 |
pomac | why not net-vlan140 | 13:17 |
*** neilus has joined #openstack-kolla | 13:18 | |
tyrola | Sorry, I had no coffee yet. Sure that would be the easiest solution. Thanks to ansible and the power of renaming network devices :D | 13:20 |
*** skramaja has quit IRC | 13:20 | |
*** inc0 has joined #openstack-kolla | 13:20 | |
inc0 | o/ | 13:22 |
*** caowei_ has joined #openstack-kolla | 13:22 | |
inc0 | interesting times coming | 13:22 |
bjolo | sup inc0 | 13:23 |
*** schwicht has joined #openstack-kolla | 13:23 | |
inc0 | election results | 13:23 |
bjolo | https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Naming_Scheme_for_VLAN_Interfaces.html | 13:24 |
inc0 | I'm imigrant in country that just elected president shouting to fight imigrants | 13:24 |
britthouser | I laugh, and then I cry, and then I laugh, and then I cry. | 13:24 |
bjolo | tyrola, ^^ | 13:24 |
bjolo | takes a fool to remain sane | 13:24 |
*** duonghq has joined #openstack-kolla | 13:24 | |
duonghq | today we have meeting as usual? | 13:24 |
inc0 | yes | 13:24 |
inc0 | we're back in business | 13:24 |
zhubingbing | hi inc0 | 13:25 |
zhubingbing | nice meet you | 13:25 |
*** lamt has quit IRC | 13:25 | |
inc0 | wassup zhubingbing ? | 13:25 |
*** jistr is now known as jistr|brb | 13:26 | |
zhubingbing | https://review.openstack.org/#/c/353261/ | 13:26 |
zhubingbing | can u help me | 13:27 |
zhubingbing | ~~) | 13:27 |
zhubingbing | review it | 13:27 |
duonghq | roger inc0 | 13:28 |
sdake | morning peeps | 13:29 |
duonghq | pbourke, ping | 13:29 |
duonghq | moring sdake | 13:29 |
sdake | inc0 rhallisey's spec gaining steam | 13:29 |
sdake | inc0 have you had a look? | 13:29 |
sdake | sup zhubingbing sup duonghq | 13:29 |
zhubingbing | hi | 13:29 |
zhubingbing | sdake | 13:29 |
sdake | inc0 i wont make it to meeting, at cncf | 13:29 |
inc0 | sdake, not today, I'm thinking about starting drinking early | 13:29 |
bjolo | http://quotespics.com/wp-content/quote-images/give-a-fuck.jpg | 13:29 |
sdake | bjolo pretty much ;-) | 13:30 |
sdake | sup bjolo | 13:30 |
*** lamt has joined #openstack-kolla | 13:31 | |
*** schwicht has quit IRC | 13:31 | |
*** dave-mccowan has joined #openstack-kolla | 13:34 | |
*** jheroux has joined #openstack-kolla | 13:34 | |
*** tonanhngo has joined #openstack-kolla | 13:35 | |
*** tonanhngo has quit IRC | 13:36 | |
tyrola | bjolo, is there a easy way in CentOS to rename a vlan device? It seems like it must contain a . (dot). | 13:38 |
bjolo | change the name in /etc/sysconfig/network-scripts/<device> | 13:39 |
*** tonanhngo has joined #openstack-kolla | 13:39 | |
tyrola | thats my ifcfg http://pastebin.com/LZcsbfV1 | 13:39 |
bjolo | ifcfg-xyz | 13:39 |
tyrola | - is also okay? i've tried it just with ifnetwork140 and the network does not work after reboot | 13:39 |
*** schwicht has joined #openstack-kolla | 13:40 | |
*** b_bezak has quit IRC | 13:40 | |
*** neilus has quit IRC | 13:40 | |
*** b_bezak has joined #openstack-kolla | 13:40 | |
bjolo | whats the name of the file? | 13:41 |
tyrola | I name it always like the device name | 13:41 |
bjolo | no, i meant the file name is usually ifcfg-<device name> | 13:41 |
bjolo | in my case i have ifcfg-bond0 and ifcfg-bond0.802 as vlan device of bond0 | 13:41 |
tyrola | yes the network interface itself uses ifcfg-ifnetwork. and the vlan interface is called ifcfg-ifnetwork.140 | 13:42 |
*** b_bezak_ has joined #openstack-kolla | 13:42 | |
bjolo | tyrola, that should work i quess | 13:42 |
tyrola | Yes it works but kolla (ansible) does not like the . char in the name if the interface | 13:43 |
bjolo | but im not sure about calling a nic "ifnetwork" | 13:43 |
duonghq | iirc you should espace this character | 13:43 |
bjolo | kolla should work fine as long as you quote the name | 13:43 |
tyrola | how can i escape it in the yml file? | 13:43 |
*** lrensing has joined #openstack-kolla | 13:43 | |
bjolo | tunnel_interface: "bond0.820" | 13:44 |
tyrola | network_interface: "ifnetwork.140" | 13:44 |
bjolo | yes | 13:44 |
tyrola | But it seems like ansible thinks .140 is a attribute of ifnetwork | 13:44 |
tyrola | fatal: [controller01] => {'msg': 'One or more items failed.', 'failed': True, 'changed': False, 'results': [{'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_ifnetwork.140'", 'failed': True}]} | 13:44 |
bjolo | mitaka you said? | 13:45 |
tyrola | yes | 13:45 |
bjolo | or newton | 13:45 |
bjolo | mitaka | 13:45 |
tyrola | mitaka branch | 13:45 |
*** b_bezak has quit IRC | 13:45 | |
bjolo | build your own images? | 13:45 |
tyrola | yes with centos7 containers and rdo | 13:45 |
tyrola | build just a few days ago | 13:45 |
bjolo | and this is from deploy? | 13:46 |
tyrola | yes | 13:46 |
bjolo | pip list | grep kolla | 13:46 |
*** jistr|brb is now known as jistr | 13:46 | |
tyrola | ls | 13:47 |
bjolo | or are you runing from git | 13:47 |
tyrola | directly from git | 13:47 |
tyrola | not installed with pip | 13:47 |
openstackgerrit | zhubingbing proposed openstack/kolla: add panko role https://review.openstack.org/394298 | 13:47 |
bjolo | ok | 13:47 |
bjolo | do you have the same network interface names on all nodes? | 13:48 |
*** egonzalez90 has quit IRC | 13:48 | |
*** egonzalez has joined #openstack-kolla | 13:48 | |
tyrola | Do you if it has been fixed in kolla in the last few days? If yes it maybe its missing in our fork. | 13:48 |
tyrola | yes I have | 13:48 |
bjolo | i run newton (or trying to) not really keeping track of mitaka branch | 13:48 |
bjolo | git log | 13:49 |
tyrola | I will check | 13:49 |
bjolo | if you ask me, i would not run a dedicated network for api | 13:49 |
bjolo | well depends on how you set things up at large | 13:49 |
sdake | inc0 i dont have my passwd for freenode, can you change the topic to something more appropriate | 13:49 |
sdake | 3.0.1 is in the past now :) | 13:50 |
*** DTadrzak has quit IRC | 13:50 | |
tyrola | Due some company security limitations we can't run the api network in the same network like the external subnets on the compute nodes, we are using neutron with bridge and provider networks. | 13:51 |
tyrola | So the ifnetwork in my case also contains vlans for external network access | 13:51 |
sdake | tyrola are you using ansible 2.z? | 13:52 |
sdake | tyrola you can find out via pip show kolla | 13:53 |
sdake | rather pip show ansible | 13:53 |
sdake | or ansible --version | 13:53 |
tyrola | Okay I think the git fork is a little bit older :( It seems like we are running a older kolla version with ansible 1.9. I will check if it's possible to upgrade. | 13:54 |
tyrola | We did a lot of modifications (added many storage roles) for our HP 3par storage. Not so easy to merge. | 13:55 |
tyrola | Oh it seems the stable/mitaka branch still using ansible 1.9 | 13:59 |
*** schwicht has quit IRC | 13:59 | |
*** portdirect has joined #openstack-kolla | 14:00 | |
*** jtriley has joined #openstack-kolla | 14:02 | |
*** schwicht has joined #openstack-kolla | 14:04 | |
tyrola | Okay seems really like ansible can't use {{ hostvars[host]['ansible_hostname'] }} {{ hostvars[host]['ansible_' + hostvars[host]['api_interface']]['ipv4']['address'] }} correctly with a dot. | 14:04 |
*** schwicht has quit IRC | 14:07 | |
*** fguillot has joined #openstack-kolla | 14:07 | |
*** eaguilar has joined #openstack-kolla | 14:09 | |
*** lrensing has quit IRC | 14:10 | |
*** nradojevic has quit IRC | 14:13 | |
openstackgerrit | Steven Dake proposed openstack/kolla-kubernetes: Add advisory language to specs directory for kolla-kubernetes https://review.openstack.org/395636 | 14:15 |
sdake | tyrola mitaka uses ansible 2.0 | 14:16 |
sdake | hrm wait its 1.9 | 14:16 |
* sdake brain waking up - wtb caffiene :) | 14:17 | |
sdake | tyrola can you ping Jeffrey4l he understands htis problem in detail | 14:17 |
*** jrist has quit IRC | 14:17 | |
*** b_bezak_ has quit IRC | 14:19 | |
*** b_bezak has joined #openstack-kolla | 14:19 | |
*** jrist has joined #openstack-kolla | 14:20 | |
*** schwicht has joined #openstack-kolla | 14:23 | |
openstackgerrit | zhubingbing proposed openstack/kolla: Add trove role https://review.openstack.org/354901 | 14:24 |
*** b_bezak has quit IRC | 14:24 | |
*** schwicht has quit IRC | 14:28 | |
*** neilus has joined #openstack-kolla | 14:28 | |
sdake | kfox1111 around? | 14:29 |
tyrola | sdake, alright. I contact him. thanks. | 14:29 |
sdake | tyrola note he is in china | 14:29 |
sdake | usuually he is aroudn this hour | 14:29 |
*** lrensing has joined #openstack-kolla | 14:30 | |
sdake | but if not, you can always try the ml | 14:30 |
*** yingjun has joined #openstack-kolla | 14:31 | |
openstackgerrit | Wang Liming proposed openstack/kolla: update source doc kuryr-guide.rst and manila-hnas-guide.rst character error https://review.openstack.org/395638 | 14:33 |
*** neilus has quit IRC | 14:33 | |
*** f13o_ has joined #openstack-kolla | 14:36 | |
*** schwicht has joined #openstack-kolla | 14:36 | |
*** f13o has quit IRC | 14:41 | |
*** schwicht has quit IRC | 14:41 | |
openstackgerrit | Wei Cao proposed openstack/kolla: Add karbor container https://review.openstack.org/395006 | 14:42 |
openstackgerrit | Wang Liming proposed openstack/kolla: update production-architecture-guide.rst Some words that are wrong in grammar https://review.openstack.org/395645 | 14:43 |
*** schwicht has joined #openstack-kolla | 14:45 | |
*** schwicht has quit IRC | 14:52 | |
*** b_bezak has joined #openstack-kolla | 14:54 | |
*** srwilkers has joined #openstack-kolla | 14:58 | |
*** schwicht has joined #openstack-kolla | 15:00 | |
*** saneax-_-|AFK is now known as saneax | 15:03 | |
*** zhurong has quit IRC | 15:03 | |
*** schwicht has quit IRC | 15:04 | |
*** neilus has joined #openstack-kolla | 15:10 | |
*** DTadrzak has joined #openstack-kolla | 15:12 | |
*** schwicht has joined #openstack-kolla | 15:12 | |
*** diogogmt has quit IRC | 15:13 | |
*** saneax is now known as saneax-_-|AFK | 15:14 | |
*** caowei_ has quit IRC | 15:14 | |
*** saneax-_-|AFK is now known as saneax | 15:14 | |
*** jtriley has quit IRC | 15:15 | |
*** DTadrzak has quit IRC | 15:16 | |
*** schwicht has quit IRC | 15:17 | |
*** msimonin has joined #openstack-kolla | 15:23 | |
*** rhallisey has joined #openstack-kolla | 15:24 | |
*** inc0 has quit IRC | 15:26 | |
*** inc0 has joined #openstack-kolla | 15:27 | |
rhallisey | morning | 15:27 |
lrensing | morning | 15:27 |
*** msimonin has quit IRC | 15:29 | |
srwilkers | morning rhallisey | 15:29 |
*** jtriley has joined #openstack-kolla | 15:31 | |
*** saneax is now known as saneax-_-|AFK | 15:32 | |
*** yingjun has quit IRC | 15:33 | |
*** yingjun has joined #openstack-kolla | 15:33 | |
*** saneax-_-|AFK is now known as saneax | 15:33 | |
*** absubram has joined #openstack-kolla | 15:33 | |
*** absubram_ has joined #openstack-kolla | 15:34 | |
inc0 | reminder guys, meeting in 26min | 15:36 |
inc0 | daylight savings | 15:36 |
inc0 | had saved our daylight once more | 15:36 |
*** CBR09 has joined #openstack-kolla | 15:37 | |
*** absubram has quit IRC | 15:38 | |
*** absubram_ is now known as absubram | 15:38 | |
*** yingjun has quit IRC | 15:38 | |
*** schwicht has joined #openstack-kolla | 15:39 | |
srwilkers | damn you DST | 15:40 |
openstackgerrit | Pete Birley proposed openstack/kolla: Add Custom template path option to kolla-build https://review.openstack.org/395676 | 15:41 |
*** nradojevic has joined #openstack-kolla | 15:42 | |
*** egonzalez90 has joined #openstack-kolla | 15:42 | |
*** egonzalez has quit IRC | 15:43 | |
*** TxGirlGeek has joined #openstack-kolla | 15:44 | |
inc0 | portdirect, I had a bit different idea about this | 15:44 |
inc0 | how about "template append path"? | 15:44 |
inc0 | default kolla path plus tpls from specified dir | 15:45 |
inc0 | instead of full new dir | 15:45 |
*** schwicht has quit IRC | 15:45 | |
*** sdake has quit IRC | 15:50 | |
openstackgerrit | Pete Birley proposed openstack/kolla: Add Custom template path option to kolla-build https://review.openstack.org/395676 | 15:51 |
*** tonanhngo_ has joined #openstack-kolla | 15:51 | |
*** tonanhngo has quit IRC | 15:51 | |
*** sdake has joined #openstack-kolla | 15:52 | |
*** ayoung has joined #openstack-kolla | 15:55 | |
*** msimonin has joined #openstack-kolla | 15:55 | |
sdake | inc0 i will make meeting today if i can | 15:55 |
sdake | pbourke you about | 15:55 |
pbourke | sdake: yeah | 15:55 |
*** tonanhngo_ has quit IRC | 15:55 | |
sdake | pbourke is stvnoyes1 interested in the operator spec ryan has produced | 15:55 |
sdake | oh hes here ;) | 15:56 |
sdake | stvnoyes1 are you interested in the operator spec ryan has produced | 15:56 |
sdake | stvnoyes1 if so, plz add your name to the list of assignees :) | 15:56 |
zhubingbing | later we should start meeting | 15:57 |
stvnoyes1 | sdake: mgiles will be working on that. I've been given another set of work so unfortunately I won't be able to take this on atm. I'll talk to mark and have him added. | 15:57 |
inc0 | 2 more minutes:) | 15:57 |
openstackgerrit | James McCarthy proposed openstack/kolla: Missing customization of tenant network https://review.openstack.org/394988 | 15:58 |
rhallisey | sdake, can we go straight to Go? | 15:59 |
sdake | rhallisey nope | 15:59 |
rhallisey | ok | 15:59 |
rhallisey | thought so, those comments made it seem like we could | 15:59 |
sdake | rhallisey reason being we would need to enable the ecosystem | 15:59 |
*** schwicht has joined #openstack-kolla | 15:59 | |
sdake | fi we enabled the openstack ecosystem with go, we could do it in go | 15:59 |
rhallisey | ok I will add that detail | 15:59 |
sdake | that would be longer term work | 15:59 |
portdirect | inc0: sorry irc in background :( | 15:59 |
*** msimonin has quit IRC | 15:59 | |
sdake | stvnoyes1 roger | 15:59 |
sdake | oh is meeting in 2 minutes? | 16:00 |
rhallisey | sdake, right now | 16:00 |
portdirect | inc0: I'm ok with that idea: I'll update the pr after the meeting | 16:00 |
inc0 | thanks | 16:00 |
sdake | is the meeting now? | 16:00 |
sdake | or in 1 hr | 16:00 |
inc0 | now | 16:00 |
sdake | (no idea, traveling) | 16:00 |
sdake | ok thanks | 16:00 |
inc0 | our daylight got saved | 16:00 |
*** DTadrzak has joined #openstack-kolla | 16:01 | |
*** ayoung has quit IRC | 16:01 | |
*** eaguilar has quit IRC | 16:01 | |
*** b_bezak has quit IRC | 16:01 | |
*** saneax is now known as saneax-_-|AFK | 16:01 | |
*** saneax-_-|AFK is now known as saneax | 16:01 | |
*** saneax is now known as saneax-_-|AFK | 16:03 | |
*** schwicht has quit IRC | 16:04 | |
*** msimonin has joined #openstack-kolla | 16:05 | |
pprokop | Hi sorry for being late | 16:06 |
egonzalez90 | pprokop: #openstack-meeting-4 | 16:06 |
pprokop | thanks | 16:07 |
*** jtriley has quit IRC | 16:10 | |
*** neilus has quit IRC | 16:11 | |
sdake | say stvnoyes1 - we have our kolla irc meeting now in openstack-meeting-4 if your interested | 16:11 |
*** schwicht has joined #openstack-kolla | 16:11 | |
*** saneax-_-|AFK is now known as saneax | 16:13 | |
openstackgerrit | Merged openstack/kolla: add panko dockerfile https://review.openstack.org/387232 | 16:14 |
*** schwicht has quit IRC | 16:16 | |
*** jtriley has joined #openstack-kolla | 16:17 | |
*** absubram has quit IRC | 16:17 | |
*** Marcellin__ has joined #openstack-kolla | 16:20 | |
*** CBR09 has quit IRC | 16:20 | |
*** saneax is now known as saneax-_-|AFK | 16:22 | |
*** saneax-_-|AFK is now known as saneax | 16:22 | |
*** saneax is now known as saneax-_-|AFK | 16:23 | |
*** saneax-_-|AFK is now known as saneax | 16:23 | |
*** schwicht has joined #openstack-kolla | 16:26 | |
*** schwicht has quit IRC | 16:26 | |
*** schwicht has joined #openstack-kolla | 16:27 | |
*** nradojevic has quit IRC | 16:30 | |
*** msimonin has quit IRC | 16:31 | |
*** schwicht has quit IRC | 16:32 | |
*** saneax is now known as saneax-_-|AFK | 16:33 | |
*** jemcevoy has quit IRC | 16:33 | |
*** saneax-_-|AFK is now known as saneax | 16:34 | |
*** berendt has joined #openstack-kolla | 16:35 | |
*** saneax is now known as saneax-_-|AFK | 16:37 | |
*** saneax-_-|AFK is now known as saneax | 16:37 | |
*** schwicht has joined #openstack-kolla | 16:38 | |
*** sean-k-mooney has quit IRC | 16:39 | |
*** msimonin has joined #openstack-kolla | 16:39 | |
*** strigazi is now known as strigazi_AFK | 16:39 | |
*** sean-k-mooney has joined #openstack-kolla | 16:40 | |
*** saneax is now known as saneax-_-|AFK | 16:40 | |
*** saneax-_-|AFK is now known as saneax | 16:41 | |
*** AnswerGu1 has joined #openstack-kolla | 16:41 | |
*** fragatina has joined #openstack-kolla | 16:42 | |
*** schwicht has quit IRC | 16:43 | |
*** f13o_ has quit IRC | 16:44 | |
*** msimonin has quit IRC | 16:44 | |
bjolo | pbourke, around? | 16:45 |
openstackgerrit | zhubingbing proposed openstack/kolla: Add trove role https://review.openstack.org/354901 | 16:45 |
*** jemcevoy has joined #openstack-kolla | 16:46 | |
pbourke | bjolo: hey bjorn! | 16:46 |
*** saneax is now known as saneax-_-|AFK | 16:46 | |
*** saneax-_-|AFK is now known as saneax | 16:46 | |
*** msimonin has joined #openstack-kolla | 16:49 | |
AnswerGu1 | So, after a success build (--base ubuntu --type source --tag 3.0.0) and deploy ... after I source admin-openrc.sh ... when I try to run ./tools/init-runonce I get: Configuring neutron. | 16:49 |
AnswerGu1 | <html><body><h1>503 Service Unavailable</h1> | 16:49 |
AnswerGu1 | No server is available to handle this request. | 16:49 |
AnswerGu1 | .... 11 times | 16:49 |
AnswerGu1 | (once for each neutron invocation in the init-runonce script). | 16:50 |
*** saneax is now known as saneax-_-|AFK | 16:50 | |
*** saneax-_-|AFK is now known as saneax | 16:50 | |
AnswerGu1 | docker -ps | neutron shows the services running except for this: | 16:50 |
*** bmace has quit IRC | 16:50 | |
*** n3v3rm0r3r has quit IRC | 16:50 | |
*** bmace has joined #openstack-kolla | 16:50 | |
AnswerGu1 | 43f27xxxxxxx 10.1.xx.xx:4000/kolla/ubuntu-source-neutron-server:3.0.0 \ | 16:51 |
AnswerGu1 | "kolla_start" 2 hours ago Restarting (1) 20 minutes ago | 16:51 |
bjolo | pbourke, weekly ongoing... | 16:51 |
bjolo | pbourke, i have some issues with multiple external networks | 16:51 |
bjolo | pbourke, thought i pick your brain on it | 16:51 |
bjolo | pbourke, singel external works, but multiple does not. traffic does not get out | 16:52 |
egonzalez90 | AnswerGu1: what does docker logs neutron_server return? | 16:52 |
*** saneax is now known as saneax-_-|AFK | 16:52 | |
*** saneax-_-|AFK is now known as saneax | 16:53 | |
pbourke | bjolo: hmm ok so I remember you were having issues with this, just trying to remember exactly. I think you were missing the patch that configured the bridges in openvswitch? | 16:53 |
AnswerGu1 | I'm looking for that now. | 16:53 |
bjolo | pbourke, im past that point | 16:53 |
*** msimonin has quit IRC | 16:53 | |
bjolo | the deploy works, bridges created etc. the issue is that traffic does not find its way out to external network | 16:54 |
pbourke | hmm ok | 16:54 |
*** saneax is now known as saneax-_-|AFK | 16:54 | |
bjolo | it seems packets are dropped by br-int openflow rules on network node | 16:54 |
AnswerGu1 | egonzalez90: the tail of my docker logs for the neutron-server container: | 16:55 |
AnswerGu1 | Running command: 'neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_lbaas.conf --config-file /etc/neutron/neutron_vpnaas.conf' | 16:55 |
AnswerGu1 | Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports. | 16:55 |
bjolo | like it goes out the router but br-int cant find the external bridge | 16:55 |
AnswerGu1 | Wo we have a preferred pastebin? | 16:55 |
egonzalez90 | AnswerGu1: please paste it in paste.openstack.org | 16:55 |
AnswerGu1 | I'm looking to see if this bug applies to me: https://bugs.launchpad.net/kolla/+bug/1592418 | 16:56 |
openstack | Launchpad bug 1592418 in kolla "neutron-agent container not working with type source and neutron lbaas enabled" [High,Confirmed] - Assigned to Christian Berendt (berendt) | 16:56 |
pomac | pbourke: it also looks like the interface does the wrong source route | 16:57 |
pomac | pbourke: it doesnt answer with the local ip but with the external ip - which is the ignored by the vm | 16:58 |
*** schwicht has joined #openstack-kolla | 16:58 | |
*** DTadrzak has quit IRC | 16:59 | |
rhallisey | ok continue with any discussion | 16:59 |
* rhallisey needs food | 16:59 | |
inc0 | portdirect, https://www.youtube.com/watch?v=9VDvgL58h_Y | 16:59 |
portdirect | awesome :) | 17:00 |
AnswerGu1 | egonzalez90: http://paste.openstack.org/show/588595/ | 17:00 |
duonghq | pbourke, ping | 17:00 |
srwilkers | inc0: fitting with the atmosphere today | 17:01 |
pbourke | pomac: bjolo: hmm ok I haven't seen this | 17:01 |
*** msimonin has joined #openstack-kolla | 17:01 | |
pbourke | pomac: bjolo: but if you both are it sounds like a problem | 17:01 |
*** eaguilar has joined #openstack-kolla | 17:01 | |
jascott1 | inc0 morning! are we meeting? | 17:01 |
bjolo | we are sitting together | 17:01 |
bjolo | pomac is my colleague | 17:01 |
inc0 | jascott1, daylight didnt save you | 17:01 |
duonghq | pbourke, can you give some opinions about new comment from Jeffrey4l and egonzalez90 in https://review.openstack.org/#/c/394260/ | 17:01 |
qwang | pprokop: sorry I was late this mornig | 17:01 |
inc0 | we just finished | 17:02 |
jascott1 | i was up | 17:02 |
jascott1 | oh | 17:02 |
jascott1 | dang | 17:02 |
jascott1 | whatd i miss? | 17:02 |
qwang | i joined the meeting for the second half but didn't say anything. it was too tense | 17:02 |
inc0 | flame war:) | 17:02 |
inc0 | read the logs | 17:02 |
portdirect | I put together a rough PoC for kolla build that squashes image layers in a dockerfile into a single image (https://review.openstack.org/#/c/392115/). it saves about 30% of the base image size and potentially frees us up to make some further optimisations (like removing gcc and dev libs) for source containers. | 17:02 |
pprokop | Just opensource | 17:02 |
*** neilus has joined #openstack-kolla | 17:03 | |
duonghq | rhallisey, ping | 17:03 |
pprokop | Friday is an holiday in Poland | 17:03 |
jascott1 | aight thx | 17:03 |
* jascott1 adjusts his sundial | 17:03 | |
pprokop | so probably Monday is fine just ping me what time | 17:03 |
*** schwicht has quit IRC | 17:03 | |
duonghq | sdake, ping | 17:04 |
rhallisey | duonghq, hey | 17:04 |
duonghq | sdake, you still in conference? | 17:04 |
rhallisey | duonghq, so you mentioned deps with ansible | 17:04 |
pbourke | bjolo: aha. let me check with some others here and see if they're come across this | 17:04 |
portdirect | docker is putting similar functionallity upstream - but is squashes all layers into a single one (meaning massive pulls...) if anyone's interested I could develop this further, my experience is that it can knock quite a signifigant amount of space (~40%) off images. | 17:04 |
duonghq | rhallisey, yep, I mean cross-projects dependency | 17:05 |
duonghq | rhallisey, e.g. Magnum depends on Heat | 17:05 |
*** schwicht has joined #openstack-kolla | 17:05 | |
*** tonanhngo has joined #openstack-kolla | 17:05 | |
sdake | duonghq trying to be | 17:05 |
sdake | duonghq need to shower | 17:06 |
*** zhubingbing has quit IRC | 17:06 | |
sdake | spit it out | 17:06 |
pprokop | and about choreography and orchestration (pretty good post) http://stackoverflow.com/questions/4127241/orchestration-vs-choreography | 17:06 |
duonghq | sdake, wish that you can review ansible-become bp implementation: start with https://review.openstack.org/#/c/358539/ after the shower | 17:07 |
sdake | pprokop thanks for link | 17:07 |
pprokop | :) my pleasure | 17:07 |
sdake | duonghq i dont have time for reviews today sorry | 17:07 |
sdake | we have a large core review team, assume they will get to it eventually :) | 17:07 |
*** neilus has quit IRC | 17:07 | |
rhallisey | duonghq, what about it specifcally? | 17:07 |
duonghq | sdake, I asked you just because you approved my bp, sorry | 17:08 |
duonghq | rhallisey, most basic example is every service depends on Keystone (in most case), we addressed it well. | 17:08 |
rhallisey | duonghq, right, ansible worked great for that | 17:09 |
duonghq | but for upcoming service, iirc we have not had any general mechanism for declare the deps graph | 17:09 |
*** vbel has joined #openstack-kolla | 17:09 | |
sdake | pprokop ok reading the first response which is pretty good and represents my understanding of entrypoint and operators | 17:09 |
*** tonanhngo has quit IRC | 17:09 | |
*** schwicht has quit IRC | 17:09 | |
sdake | "This means that a choreography differs from an orchestration with respect to where the logic that controls the interactions between the services involved should reside." | 17:09 |
*** vbel has quit IRC | 17:10 | |
egonzalez90 | agree with duonghq , as your previous example of magnum with heat | 17:10 |
*** tonanhngo has joined #openstack-kolla | 17:10 | |
sdake | I am not keen on having the containers changed | 17:10 |
inc0 | sdake, we can introduce new container, brand new | 17:10 |
inc0 | which will act as init container | 17:10 |
sdake | that is what an action container i s! | 17:10 |
sdake | sorry not action container | 17:10 |
inc0 | it's sole purpose will be to not run until deps are met | 17:11 |
rhallisey | inc0, what I'm worried about is can you solved all cases of that problem for OpenStack | 17:11 |
pprokop | that is why you can control it via envs | 17:11 |
inc0 | I can't think of case that couldn't be solved | 17:12 |
pprokop | and only thing you provide | 17:12 |
*** jtriley has quit IRC | 17:12 | |
pprokop | is a name of k8s service,job, ds | 17:12 |
sdake | inc0 what you propose is exactly what an operator container is | 17:13 |
rhallisey | so the env is provided on the fly to list deps | 17:13 |
sdake | inc0 except operator contaienr does some bootstrapping as well | 17:13 |
pprokop | each deployment is different and Helm just have to template those envs | 17:13 |
inc0 | sdake, not exactly | 17:14 |
pprokop | in entrypoint approach k8s jobs does bootstraping and you just append K8s_JOB env | 17:14 |
inc0 | as operator will run the logic itself | 17:14 |
inc0 | question, what happends if operator dies? | 17:14 |
sdake | inc0 no, operator runs a controller | 17:14 |
sdake | inc0 controller rusn the logic itself | 17:14 |
rhallisey | inc0, doesn't matter if it dies | 17:14 |
sdake | its the same thing exactly | 17:14 |
rhallisey | ppalacios, what about upgrading though | 17:14 |
*** matrohon has quit IRC | 17:14 | |
rhallisey | oops | 17:14 |
sdake | i guess this raises a new question as we head down the rabbit hole | 17:14 |
rhallisey | pprokop, what about upgrading though | 17:14 |
sdake | shoudl we use entrypoint in our operator containers | 17:15 |
rhallisey | dep logic | 17:15 |
pprokop | follow k8s way update images perform rolling update and run job for db-sync | 17:15 |
rhallisey | that part I'm scared of | 17:16 |
inc0 | you don't really deal with deps during upgrade | 17:16 |
pprokop | yes | 17:16 |
pprokop | OVO works ? | 17:16 |
inc0 | only dep is "run db sync" -> "run upgrade" | 17:16 |
inc0 | ovo deal with different issue | 17:17 |
duonghq | rolling upgrade and then 0-downtime upgrade for db and ovo is different service-to-service | 17:17 |
pprokop | ok | 17:17 |
sdake | right - which requires an operator | 17:17 |
rhallisey | it's a workflow, you'll need to to these things in order | 17:17 |
rhallisey | an op will not trust if you don't | 17:17 |
sdake | ya we have to keep in mind here folks, we have built up a "16% interest" in kolla (the ansible part) in the operator community (data from last user survey) | 17:18 |
rhallisey | I mean k8s rolling upgrade is fantastic, but there operation is a huge pain point for ops | 17:18 |
rhallisey | because it's so sensitive | 17:18 |
sdake | if the Operators (the people using kolla) don't trust kolla-kubernetes | 17:18 |
sdake | it could impact kolla-ansible | 17:18 |
sdake | and Operators wont trust containers that self-magically organize | 17:19 |
inc0 | if somebody wants to run kolla-k8s, they better know what k8s before | 17:19 |
rhallisey | pprokop, idk just some thoughts. I think kfox1111 will have some input on the matter | 17:19 |
sdake | ya - so gotta jet folks | 17:19 |
sdake | goign to hit the floor with your questions | 17:19 |
duonghq | I noticed that we have not implemented rolling upgrade properly in kolla-ansible for most services, if me if I wrong | 17:19 |
sdake | and see what people think of entrypoint | 17:19 |
inc0 | rhallisey, I'm positive we can make it transparent enough for good debug | 17:19 |
rhallisey | I think k8s rolling update looks great and can be great for updates, but I want to be super careful | 17:19 |
inc0 | it's not matter of arch, it's matter of toolset | 17:20 |
portdirect | sdake: lates :) | 17:20 |
portdirect | *laters | 17:20 |
inc0 | k8s rolling upgrades is simple thing | 17:20 |
inc0 | upgrade pod one at the time | 17:20 |
inc0 | that's it | 17:20 |
rhallisey | it is and that I suppose is part of the probelm | 17:20 |
rhallisey | because openstack is not a simple upgrade | 17:20 |
duonghq | inc0, in this aspect, serial from ansible is nearly the same | 17:21 |
duonghq | but the hardest part is other | 17:21 |
inc0 | duonghq, exactly | 17:21 |
rhallisey | ok I'll brb | 17:21 |
rhallisey | pprokop, curious about the demo. Also keep posting in the spec. Super appreciate it! :) | 17:21 |
rhallisey | the PoCs should help | 17:22 |
*** MarMat has joined #openstack-kolla | 17:22 | |
ppalacios | rhallisey: that was not for me, right? | 17:23 |
pprokop | Okay :D | 17:23 |
duonghq | we can rolling upgrade service binary/code very easily with out toolset, but if we only do that, maybe something'll break when major version upgrade is done | 17:23 |
duonghq | example for ovo: we need turn on and off version pinning for some service | 17:24 |
duonghq | before and after rolling upgrade respectively | 17:24 |
duonghq | seem that we have not implemented this? | 17:24 |
sdake | pprokop if you are really keen to take a look at entrypoint for kolla, I think what would be feasible is something inc0 mentioned | 17:31 |
inc0 | sdake, this is what it is | 17:32 |
sdake | which is to treat it as a seperate container | 17:32 |
inc0 | we discussed that with Piotrek yesterday, and I knew this arch before | 17:32 |
inc0 | we will have dedicated "lock" container | 17:32 |
sdake | pprokop - in essence make an "operator" container using entrypoint | 17:33 |
*** n3v3rm0r3r has joined #openstack-kolla | 17:33 | |
sdake | pprokop to me, jamming entrypoint itno every one of our containers is a non-starter for a whole lot of reasons | 17:33 |
inc0 | so again, my understanding of entrypoint might fail | 17:33 |
sdake | the main one being IT DIDNT WORK IN THE PAST | 17:33 |
inc0 | but it seems like external pod that does magic | 17:33 |
pprokop | it's pointless to put it into operators | 17:34 |
inc0 | sdake, it's different approach...fundamentally... | 17:34 |
pprokop | because it was not designed to work this way | 17:34 |
bjolo | pbourke, when vm tries to ping external physical gw. arp request goes out and reply comes back, but br-int drops them it seems like | 17:34 |
bjolo | http://paste.openstack.org/show/588600/ | 17:34 |
inc0 | trust me on that if you don't want to hear lengthy explanation | 17:34 |
sdake | inc0 ok, if its fundamentallly a different approach and being taken by stackenetes and fuel-ccp, why should we use it? | 17:34 |
sdake | wouldn't that just make kolla-kubernetes fuel-ccp or stackanetes? | 17:34 |
inc0 | fundamentally different from what we had in compose | 17:34 |
inc0 | no, there are more differences | 17:35 |
rhallisey | ppalacios, sorry that was for pprokop. | 17:35 |
inc0 | also, good ideas should be spread | 17:35 |
pprokop | so you are just turning that this idea cause someone else used it ? | 17:35 |
inc0 | not being similar to stackanetes is not good reason for me to not use this tech | 17:35 |
pprokop | :D | 17:35 |
sdake | pprokop my question is why should we replicate someone elses implemetnation fo the same exact thing? | 17:35 |
inc0 | sdake, we will reuse this:) | 17:36 |
pprokop | You can just use this implementation. | 17:36 |
pprokop | Not rewrite it. | 17:36 |
inc0 | maybe tailor it to our own ends | 17:36 |
inc0 | like put it into init container instead of other containers | 17:36 |
sdake | pprokop i am more keen on operator containers | 17:36 |
sdake | with controllers inside | 17:36 |
inc0 | sdake, why? | 17:36 |
pprokop | Okay so let's make POC's. | 17:36 |
inc0 | explain me what is real benefit | 17:36 |
pprokop | And see what works best. | 17:37 |
sdake | simplicity is the benefit | 17:37 |
pprokop | It's pointless to argue. | 17:37 |
sdake | pprokop if stackanetes has got it to work, i have no doubt it can work | 17:37 |
inc0 | ok, so another try at "my understanding what operator is" | 17:37 |
sdake | reliable, not so much | 17:37 |
sdake | inc0 kfox1111 explains it well in the review | 17:37 |
inc0 | it's external pod that will query kubectl and run pods and whatnot based on what it sees in kubectl | 17:37 |
sdake | read it ;) | 17:37 |
sdake | right | 17:38 |
*** egonzalez90 has quit IRC | 17:38 | |
pprokop | This is k8s-appcontroller | 17:38 |
inc0 | how appcontroller differs from operator? | 17:38 |
pprokop | so don't write your own staff then. | 17:38 |
sdake | an operator is a container that contains an implementation of code | 17:38 |
pprokop | it is an operator in your sense. | 17:38 |
sdake | the code is called a controller | 17:38 |
pprokop | But it was created before operator name was invented. | 17:39 |
sdake | perhaps mirantis has written k8s-appcontroller | 17:39 |
sdake | but to be brutally frank, I don't trust mirantis | 17:39 |
*** schwicht has joined #openstack-kolla | 17:39 | |
sdake | i have no mistrust of coreos | 17:39 |
sdake | but i dont trust mirantis | 17:39 |
sdake | and nothing mirantis does is EVER going to change that | 17:39 |
inc0 | whatever | 17:39 |
pprokop | So this are different folks then fuel-ccp. | 17:39 |
inc0 | let's talk about ideas not companies | 17:39 |
srwilkers | playing devils advocate, but sometimes those two are intertwined inc0 | 17:40 |
sdake | pprokop operator is a container that contains a controller | 17:40 |
srwilkers | not always, but sometimes | 17:40 |
sdake | pprokop its possible k8s-appcontroller can solve our problems | 17:40 |
inc0 | srwilkers, I'm not saying use appcontroller | 17:40 |
pprokop | I undeerstand that. | 17:40 |
inc0 | but if they reimplemtn similar approach | 17:40 |
*** dwalsh has quit IRC | 17:40 | |
inc0 | let's talk about approach | 17:40 |
sdake | this falls under definiition of "planning paralysis" | 17:41 |
sdake | and "picking winners" | 17:41 |
*** TxGirlGeek has quit IRC | 17:41 | |
jowisz | hello, i`m trying to install ceilometer and cloudkitty with kolla-ansible and i`m getting this error | 17:42 |
sdake | so appcontroller is out in my book, simply because i am tired of being played by mirantis's management's strategies | 17:42 |
*** TxGirlGeek has joined #openstack-kolla | 17:42 | |
jowisz | fatal: [wcm2.stack]: FAILED! => {"changed": false, "failed": true, "msg": "The requested image does not exist: 172.20.0.250:4000/kolla/centos-binary-cloudkitty-processor:3.0.0"} | 17:42 |
sdake | entrypoint - none of the kolla-kubernetes core team is keen on for a variety of reasons | 17:42 |
pprokop | and if it goes to incubator ? | 17:42 |
jowisz | and [root@kolla-deploy BLUE/WRO ~]# docker images | grep cloudkitty | 17:42 |
jowisz | [root@kolla-deploy BLUE/WRO ~]# | 17:42 |
inc0 | please please please don't tell me we'll have to write 500loc of golang per every service in openstack https://github.com/coreos/etcd-operator/blob/master/pkg/cluster/cluster.go | 17:42 |
jowisz | how can i update docker registry? or pull missing images ? | 17:42 |
sdake | ok i gotta jet | 17:43 |
sdake | but thats a summary of where I stand on this | 17:43 |
inc0 | jowisz, https://github.com/openstack/kolla/blob/master/doc/image-building.rst proponuje budowac:) | 17:43 |
jowisz | inc0: dzięki ;) zerknę | 17:44 |
jowisz | ale kolega mnie tu pisze, ze robił kolla-build | 17:44 |
jowisz | ;) | 17:44 |
inc0 | anyway, le'ts move to english;) soo, I'm not quite sure if we have cloudkitty | 17:45 |
sean-k-mooney | inc0: there is a docker container i think | 17:46 |
jowisz | sure ;) | 17:46 |
jowisz | root@kolla-deploy BLUE/WRO ~]# kolla-build cloudkitty-base cloudkitty-api cloudkitty-processor | 17:46 |
sean-k-mooney | inc0: not sure if ansible code is there | 17:46 |
jowisz | something is building :) | 17:46 |
sean-k-mooney | jowisz: you can do "kolla-build cloudkitty" to build anything with cloudkitty in the name for future reference | 17:47 |
jowisz | sean-k-mooney: thanks :) | 17:48 |
*** duonghq has quit IRC | 17:53 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch https://review.openstack.org/393877 | 17:59 |
*** msimonin has quit IRC | 17:59 | |
*** pbourke has quit IRC | 17:59 | |
inc0 | ok we do have cloudkitty there | 17:59 |
inc0 | I can't vouch for deployment code tho | 17:59 |
jowisz | unfortunately: | 18:00 |
jowisz | ERROR:kolla.image.build.cloudkitty-base:Error'd with the following message | 18:00 |
jowisz | ERROR:kolla.image.build.cloudkitty-base:The command '/bin/sh -c echo 'binary not yet available for centos' && /bin/false' returned a non-zero code: 1 | 18:00 |
inc0 | ahh | 18:00 |
inc0 | that would make sense | 18:00 |
jowisz | ;) | 18:00 |
inc0 | so if you want hacky way to do it | 18:01 |
inc0 | build it with source and retag this name to binary | 18:01 |
inc0 | so kolla-build cloutkitty -t source | 18:01 |
*** pbourke has joined #openstack-kolla | 18:01 | |
inc0 | look what containers will be built and retag them from 172.20.0.250:4000/kolla/centos-source-cloudkitty-processor:3.0.0 to 172.20.0.250:4000/kolla/centos-binary-cloudkitty-processor:3.0.0 | 18:01 |
jowisz | inc0: ok, i will try ;) | 18:02 |
*** mkoderer has quit IRC | 18:03 | |
*** jtriley has joined #openstack-kolla | 18:03 | |
*** fragatin_ has joined #openstack-kolla | 18:04 | |
*** nhlfr_ has joined #openstack-kolla | 18:04 | |
inc0 | jowisz, remember to do docker push afterwards | 18:05 |
jowisz | sure | 18:05 |
*** Serlex has quit IRC | 18:06 | |
*** nihilifer has quit IRC | 18:07 | |
*** fragatina has quit IRC | 18:07 | |
portdirect | kfox1111: ping | 18:09 |
mliima | sdake, https://review.openstack.org/#/c/393471/ | 18:09 |
*** unicell has quit IRC | 18:09 | |
*** nihilifer has joined #openstack-kolla | 18:10 | |
portdirect | inc0: ping | 18:12 |
inc0 | here | 18:12 |
portdirect | hey - just redoing that custom image template dir stuff - are we gonna add the custom dir to the tuple to search though? | 18:14 |
portdirect | lost track of stuff during the meeting :) | 18:15 |
awiddersheim | anyone able to review? | 18:15 |
awiddersheim | https://review.openstack.org/#/c/279913/ | 18:15 |
portdirect | think that was the plan - but do you have a peference for if the custom template dir takes presendence or is last to search? | 18:16 |
inc0 | portdirect, I think if you add it it will pick first found, not sure tho | 18:16 |
inc0 | we need to merge multiple dirs really | 18:16 |
inc0 | so mignt need more coding for that | 18:17 |
*** sdake has quit IRC | 18:19 | |
portdirect | thats what I was thinking - we would need to make it search on a container by container basis - up for doing it, kfox was also wanting to have the facility to have multiple additional dirs - which makes sense. though its evening here so it''l be the moring before i get round it it. | 18:20 |
*** portdirect is now known as portdirect_away | 18:22 | |
*** ayoung has joined #openstack-kolla | 18:33 | |
*** unicell has joined #openstack-kolla | 18:36 | |
*** huikang has joined #openstack-kolla | 18:38 | |
*** fragatin_ has quit IRC | 18:47 | |
*** fragatina has joined #openstack-kolla | 18:48 | |
*** f13o has joined #openstack-kolla | 18:55 | |
*** harlowja has quit IRC | 18:59 | |
*** mliima_ has joined #openstack-kolla | 19:00 | |
*** jtriley has quit IRC | 19:02 | |
*** jtriley has joined #openstack-kolla | 19:02 | |
*** mliima has quit IRC | 19:03 | |
*** diogogmt has joined #openstack-kolla | 19:03 | |
openstackgerrit | Larry Rensing proposed openstack/kolla-kubernetes: Adding prechecks script https://review.openstack.org/394569 | 19:07 |
*** dcwangmit01 has joined #openstack-kolla | 19:08 | |
openstackgerrit | sean mooney proposed openstack/kolla: [WIP] adds support for ovs with dpdk netdev datapath https://review.openstack.org/342354 | 19:08 |
*** dcwangmit01_ has quit IRC | 19:10 | |
*** eaguilar has quit IRC | 19:10 | |
*** eaguilar has joined #openstack-kolla | 19:13 | |
*** coolsvap has quit IRC | 19:17 | |
*** dave-mccowan has quit IRC | 19:25 | |
*** dave-mccowan has joined #openstack-kolla | 19:26 | |
*** eaguilar has quit IRC | 19:28 | |
*** lrensing has quit IRC | 19:28 | |
*** eaguilar has joined #openstack-kolla | 19:28 | |
*** chas_ has quit IRC | 19:33 | |
*** dave-mccowan has quit IRC | 19:36 | |
openstackgerrit | Ryan Hallisey proposed openstack/kolla-kubernetes: Spec - Kolla-Kubernetes Deployment Architecture https://review.openstack.org/392257 | 19:40 |
*** msimonin has joined #openstack-kolla | 19:41 | |
openstackgerrit | Kevin Fox proposed openstack/kolla-kubernetes: Fix new kubeadm precheck https://review.openstack.org/395779 | 19:47 |
openstackgerrit | Merged openstack/kolla: Remove Fedora support from manilla-data https://review.openstack.org/394074 | 19:51 |
*** stvnoyes has joined #openstack-kolla | 19:52 | |
*** msimonin1 has joined #openstack-kolla | 19:54 | |
*** stvnoyes1 has quit IRC | 19:55 | |
*** msimonin has quit IRC | 19:58 | |
*** neilus has joined #openstack-kolla | 20:01 | |
*** papacz has quit IRC | 20:04 | |
*** sdake has joined #openstack-kolla | 20:08 | |
*** gfidente has quit IRC | 20:13 | |
*** lrensing has joined #openstack-kolla | 20:13 | |
openstackgerrit | Merged openstack/kolla: Update manila-data service inventory https://review.openstack.org/393471 | 20:14 |
*** n3v3rm0r3r has quit IRC | 20:16 | |
*** ayoung has quit IRC | 20:17 | |
*** eaguilar has quit IRC | 20:18 | |
*** jtriley has quit IRC | 20:18 | |
openstackgerrit | Steven Dake proposed openstack/kolla-kubernetes: Add advisory language to specs directory for kolla-kubernetes https://review.openstack.org/395636 | 20:19 |
*** ppalacios has quit IRC | 20:19 | |
*** TxGirlGeek has quit IRC | 20:24 | |
*** huikang has quit IRC | 20:25 | |
*** huikang has joined #openstack-kolla | 20:26 | |
*** TxGirlGeek has joined #openstack-kolla | 20:28 | |
*** huikang has quit IRC | 20:30 | |
*** huikang has joined #openstack-kolla | 20:33 | |
*** chas_ has joined #openstack-kolla | 20:34 | |
*** mliima_ has quit IRC | 20:36 | |
*** dave-mccowan has joined #openstack-kolla | 20:38 | |
*** v1k0d3n has joined #openstack-kolla | 20:38 | |
*** chas_ has quit IRC | 20:39 | |
v1k0d3n | inc0: hey man | 20:41 |
v1k0d3n | what's up dude. | 20:41 |
v1k0d3n | sorry missed the meeting this morning. | 20:41 |
inc0 | np, you missed quite a flame war:_) | 20:41 |
v1k0d3n | had to attend some things at the conf this morning. | 20:41 |
inc0 | I'll need to ask you about operators thingies | 20:42 |
v1k0d3n | yeah i hear. unfortunate. | 20:42 |
v1k0d3n | ok, cool. shoot. | 20:42 |
inc0 | nah, that's good, there is some disconnect somewhere | 20:42 |
inc0 | so I took a look at etcd operator | 20:42 |
inc0 | and to me it's a bunch of code in which we ourselves implement code to do stuff with etcd | 20:42 |
v1k0d3n | right. it's the longer path, i agree. | 20:43 |
inc0 | so instead of just deploying stuff, we create tool that talks to another tool (k8s) | 20:43 |
inc0 | seems...complex | 20:43 |
inc0 | what's the short path? | 20:43 |
v1k0d3n | but entrypoint is a short-term iterative approach. | 20:43 |
v1k0d3n | coreos and intel (as you know). | 20:43 |
v1k0d3n | however... | 20:43 |
inc0 | yeah, entrypoint will work | 20:43 |
v1k0d3n | CoreOS is showing a new path. | 20:43 |
v1k0d3n | one that works better. | 20:44 |
inc0 | and I'm not sure if I like it | 20:44 |
openstackgerrit | Kevin Fox proposed openstack/kolla-kubernetes: Fix new kubeadm precheck https://review.openstack.org/395779 | 20:44 |
v1k0d3n | better logic | 20:44 |
inc0 | I mean, it's the same as putting ansible playbooks into container | 20:44 |
v1k0d3n | well, have you run it? | 20:44 |
v1k0d3n | no it's not, not at all. | 20:44 |
v1k0d3n | so have another question for you... | 20:44 |
inc0 | go ahead | 20:44 |
v1k0d3n | before we go down this path. | 20:44 |
v1k0d3n | are you concerned with the time to build this solution? | 20:44 |
inc0 | yeah, and complexity to maintain it | 20:45 |
v1k0d3n | because of the debt to maintain with small group? | 20:45 |
v1k0d3n | ok | 20:45 |
v1k0d3n | i feel you. | 20:45 |
inc0 | not small group | 20:45 |
v1k0d3n | i have a meeting at 1:30 with alex polvi to discuss this. | 20:45 |
inc0 | ok | 20:45 |
v1k0d3n | what if i can get their help. would you consider more? | 20:45 |
inc0 | well, I just need to understand why | 20:45 |
v1k0d3n | have to be honest, entrypoint was the best solution until operator architecture/model announcement last week. | 20:46 |
inc0 | what's the real value and what are issues with different approaches | 20:46 |
v1k0d3n | ok, here's one immediate. | 20:46 |
v1k0d3n | ansible stays the say. | 20:46 |
inc0 | so operator model to me looks like reimplemented ansible tbh, but I might be mistaken | 20:46 |
v1k0d3n | operator logic can be plugged in with helm easily. | 20:46 |
v1k0d3n | are you familiar with kubernetes federated API? | 20:46 |
inc0 | no | 20:46 |
v1k0d3n | basically, write your own API | 20:47 |
v1k0d3n | and use with the kubernetes cluster. | 20:47 |
v1k0d3n | so with federated API, a controller can have access to the etcd backend, so it knows what is deployed and health of system. | 20:47 |
v1k0d3n | entrypoint does not. | 20:47 |
v1k0d3n | it's a build/deploy and forget. | 20:47 |
inc0 | so consider this | 20:47 |
kfox1111 | I missed a good flame war? darn. | 20:47 |
kfox1111 | :) | 20:47 |
v1k0d3n | operator has try operator logic. | 20:47 |
* kfox1111 wonders off to find a log.... | 20:48 | |
v1k0d3n | yes kfox1111 | 20:48 |
inc0 | we create entrypoint as it will deal with deploy | 20:48 |
inc0 | and deps | 20:48 |
srwilkers | hey kfox1111, welcome to the party | 20:48 |
kfox1111 | :) | 20:48 |
v1k0d3n | btw... kfox1111 can you weigh in your thoughts on entrypoint vs operator logic (if you know about each). | 20:48 |
inc0 | and on the side we create operator with toolset required for debugging, maintainng and whatnot | 20:48 |
v1k0d3n | inc0: i have to be honest...entrypoint is a bandaid quickpath. | 20:48 |
inc0 | so let's discuss this, why? | 20:49 |
v1k0d3n | inc0: deals with deploy....and forget it. | 20:49 |
inc0 | not really | 20:49 |
v1k0d3n | *sigh | 20:49 |
kfox1111 | which one is the entrypoint thing? | 20:49 |
inc0 | also will deal with all the restart, full downtime of cluster and whatnot | 20:49 |
v1k0d3n | i just need to be clear.... | 20:49 |
kfox1111 | that the process that slips in the container init to block it from starting until ready? | 20:49 |
v1k0d3n | we need logic of an operator. | 20:49 |
inc0 | kfox1111, entrypoint would be init-container that will wait for all the deps to be met | 20:49 |
v1k0d3n | it's new, i agree. | 20:49 |
kfox1111 | ah. | 20:50 |
rhallisey | kfox1111, lol yes :) | 20:50 |
v1k0d3n | however...that is the future | 20:50 |
kfox1111 | actually, I think both have their place in a way. | 20:50 |
rhallisey | v1k0d3n, we're trying to outline this in the spec | 20:50 |
inc0 | operator smells to me like an abstraction layer over an abstraction layer (k8s) | 20:50 |
kfox1111 | i for sure believe the orchestration/workflow logic has no buisness what so ever being in the normal containers. | 20:50 |
v1k0d3n | it is the theme that is reenforced at this conference i'm at right now. | 20:50 |
openstackgerrit | Larry Rensing proposed openstack/kolla-kubernetes: Adding prechecks script https://review.openstack.org/394569 | 20:50 |
rhallisey | but ultimatly I think the poc will tell the most | 20:50 |
v1k0d3n | one of the reason i wanted to go to this was to share back. | 20:50 |
v1k0d3n | so i'm sharing :) | 20:51 |
kfox1111 | the endpoint thing is just a way to block until deps come up, for containers that don't just do the right thing already when their deps are not up. | 20:51 |
inc0 | god I wish I could have this discussion out there | 20:51 |
rhallisey | kfox1111, flame war is a good read :) | 20:51 |
kfox1111 | ideally the daemon itself (nova-api) would just block until its deps, mariadb comes up. not crash. | 20:51 |
v1k0d3n | ok... inc0 i have an ask | 20:52 |
v1k0d3n | please.... | 20:52 |
kfox1111 | hmm.. yup. its long. wil read. :) | 20:52 |
v1k0d3n | go out to the helm group. go out to kubernetes. start asking about operators. | 20:52 |
v1k0d3n | they are not the same thing. | 20:52 |
v1k0d3n | and also... | 20:52 |
kfox1111 | I still lothe that term. :/ | 20:52 |
v1k0d3n | logically | 20:52 |
v1k0d3n | COREOS is the team behind entrypoint | 20:52 |
kfox1111 | I'm an operator. | 20:52 |
v1k0d3n | and NOW operator. | 20:52 |
kfox1111 | now an otomiton is stealing the term. :) | 20:53 |
v1k0d3n | lol | 20:53 |
kfox1111 | but seriously, | 20:53 |
kfox1111 | it makes it hard to disucss our users. | 20:53 |
srwilkers | theyre sticking you in software kfox | 20:53 |
v1k0d3n | should be controller, but don't want to go there. | 20:53 |
srwilkers | beware | 20:53 |
v1k0d3n | lo | 20:53 |
v1k0d3n | lol | 20:53 |
inc0 | v1k0d3n, I'm not defending entrypoint as the best solution there is | 20:53 |
kfox1111 | "human operator does x" "operator does y" | 20:53 |
srwilkers | welcome to the matrix | 20:53 |
inc0 | I just took a look at etcd operator and saw couple k lines of golang | 20:53 |
kfox1111 | I don't think coreos developing both technologies is nessisarily bad. | 20:53 |
inc0 | I don't want to maintain multi-thousand loc files per service | 20:54 |
kfox1111 | I think they fill different gaps for the most part, with a bit of overlap. | 20:54 |
v1k0d3n | i think some meetings need to be had | 20:54 |
v1k0d3n | this group (cores) and coreos and helm | 20:54 |
inc0 | possibly, I might misunderstand stuff | 20:54 |
kfox1111 | the deal with etcd operator is, its a virtual human maintaining etcd with a bunch of logic. its all the worflow bits a real operator needs to do. | 20:54 |
kfox1111 | thats why its so much code. :/ | 20:55 |
v1k0d3n | look, both coreos and helm are telling us (large company) operators are the way to go, with helm managing depends building (using abstracted config maps). | 20:55 |
kfox1111 | openstack's more complicated then etcd. it will probably need quite a bit of code to orchestrate as well. | 20:55 |
inc0 | and that's what ansible normally does.. | 20:55 |
rhallisey | I mean it has to be | 20:55 |
kfox1111 | comparable to kolla/ansible/* :/ | 20:55 |
rhallisey | openstack lifecycle is challenging | 20:55 |
v1k0d3n | i don't know why there is so much resistance to it, just to implement an older concept...that will force the group to re-write ansible portion of kolla. | 20:55 |
inc0 | yeah, operator seems to me like puting ansible bootstrapping into container and call it a proud name | 20:55 |
kfox1111 | inc0: thats what it is really. | 20:56 |
v1k0d3n | and i'm saying that i can talk to alex about getting help in this repo to write the controllers. | 20:56 |
kfox1111 | it could even be done using ansible. | 20:56 |
*** psanchez has quit IRC | 20:56 | |
v1k0d3n | you only need a few. | 20:56 |
kfox1111 | the nice thing is, it hides it in containers though. ;) | 20:56 |
inc0 | only worse because youy need to reimplement ansible where you're at it | 20:56 |
kfox1111 | not really. | 20:56 |
kfox1111 | k8s does all the deployment bits. you just need to use ansible to orchestrate k8s. | 20:56 |
inc0 | from within a container | 20:57 |
kfox1111 | yeah. | 20:57 |
v1k0d3n | kfox1111: no | 20:57 |
kfox1111 | containers just packaging. | 20:57 |
inc0 | because obviously when we did that outside of container it was dirty and bad;)_ | 20:57 |
v1k0d3n | no ansible to orchestrate k8s | 20:57 |
*** slagle has quit IRC | 20:57 | |
v1k0d3n | that's a horrible path forward | 20:57 |
kfox1111 | inc0: it was visible then. ;) | 20:57 |
*** stevebaker has quit IRC | 20:57 | |
inc0 | v1k0d3n, golang instead of ansible.. | 20:57 |
kfox1111 | v1k0d3n: short term and long term goals. | 20:57 |
rhallisey | I wouldn't say you re implement ansible, but only the workflow aspect of it | 20:57 |
rhallisey | none of the layering | 20:57 |
kfox1111 | short term is to get a poc of orchestration going at all. | 20:57 |
inc0 | ansible is a workflow;) | 20:57 |
v1k0d3n | guys...helm is already written for this team | 20:57 |
rhallisey | it's really heat | 20:57 |
rhallisey | imo | 20:57 |
kfox1111 | the nice thing about operators is language doesn't matter. | 20:57 |
v1k0d3n | that's why SAP came out with the helm stuff | 20:58 |
v1k0d3n | go try it out | 20:58 |
kfox1111 | so it can be switched out by go at any time. | 20:58 |
v1k0d3n | exactly with kfox1111 that lang doesnt matter | 20:58 |
v1k0d3n | use python | 20:58 |
kfox1111 | python would work too. | 20:58 |
v1k0d3n | if there are scale issues...then use go, but i don't think there's going to be any issue | 20:58 |
v1k0d3n | use what the group knows. python. perfect. | 20:58 |
kfox1111 | yeah. the workflow bits will be pretty trivial. python would work pretty well. | 20:58 |
v1k0d3n | inc0: ansible is a BAD workflow | 20:59 |
rhallisey | kfox1111, python will be good at first. bugroger mentioned it will be a much taller task than using go | 20:59 |
inc0 | and let's use this nifty workflow tool written in python called ansible;) | 20:59 |
v1k0d3n | old | 20:59 |
v1k0d3n | not new or cloud native approach | 20:59 |
inc0 | I'm teasing now | 20:59 |
v1k0d3n | ah. hard to tell over IRC :) | 20:59 |
inc0 | but it does seem to be like putting workflow inside container | 20:59 |
kfox1111 | v1k0d3n: seperate ansible the engine from ansible the deployment tool. they are in the same tool but both don't have to be used. | 20:59 |
inc0 | and if you'd use ansible module for talking to k8s | 21:00 |
inc0 | that can be very well implemented as a playbook | 21:00 |
v1k0d3n | omg...have you used the ansible mod for kubernets? | 21:00 |
v1k0d3n | didn't work well last i tried. | 21:00 |
rhallisey | yes | 21:00 |
v1k0d3n | ok. | 21:00 |
inc0 | not saying it's good, command: kubectl... will work too | 21:00 |
rhallisey | v1k0d3n, I fixed it, but my patches aren't being accepted | 21:00 |
v1k0d3n | omg.... | 21:00 |
rhallisey | been sitting there for 6 months | 21:00 |
inc0 | ok, forget ansible | 21:00 |
inc0 | I just used is as a reference | 21:01 |
kfox1111 | rhallisey: yeah. thats a big problem. | 21:01 |
inc0 | you're putting << insert your favorite workflow mechanism >> insice a container and call it a proud name | 21:01 |
kfox1111 | I think python is prbably best tradeoff for now because of that. | 21:01 |
v1k0d3n | kubectl and ansible are not good. why would we do this when we have an awesome API, and a kubernetes project supported kubernetes deployment, and depends tool? | 21:01 |
kfox1111 | inc0: no, theres an abstraction here... | 21:01 |
kfox1111 | thirdparty resource is the contract. | 21:01 |
inc0 | you mean k8s? | 21:02 |
kfox1111 | the oprator, whatever language, consuimes it and makes it work. | 21:02 |
v1k0d3n | are you talking about federated API? | 21:02 |
kfox1111 | the language doesn't really matter to the user, only the contract does. | 21:02 |
v1k0d3n | you lost me kfox1111 | 21:02 |
kfox1111 | k. example. | 21:02 |
kfox1111 | nova-api is written in python right now. | 21:02 |
v1k0d3n | well...ok | 21:02 |
v1k0d3n | so we're getting off track | 21:02 |
kfox1111 | does random user care its in python, or that the rest-api works consistantly? | 21:02 |
v1k0d3n | so...kolla-k8s is going ansible and entrypoint? | 21:03 |
v1k0d3n | just need to know. | 21:03 |
kfox1111 | it can be rewritten in go tmorrow and I wouldnt' care. but if /v2/... breaks, I would care. | 21:03 |
rhallisey | v1k0d3n, no | 21:03 |
v1k0d3n | this is absolutely huge for us. | 21:03 |
inc0 | kfox1111, but what I mean is, we're writing workflow and putting it into container right? | 21:03 |
rhallisey | v1k0d3n, at least not atm | 21:03 |
v1k0d3n | it will be the disconnect. | 21:03 |
kfox1111 | with operators, the thirdparty entrypoint/yaml description is the contract. the api for the operator. | 21:03 |
inc0 | that's all operator is? | 21:03 |
kfox1111 | what consumes it, and makes it realize the request, is whats in the container, and what the user probably doesn't care what language its written in. | 21:03 |
kfox1111 | the interface they are using to implement operators is the k8s thirdpartyresource. | 21:05 |
rhallisey | v1k0d3n, I outlined it in the spec what's currently being considered: https://review.openstack.org/#/c/392257/ | 21:05 |
kfox1111 | which is just a way to extend k8s with new object types. | 21:05 |
kfox1111 | so, say, assuming you had a single openstack operator for all of kolla. | 21:05 |
kfox1111 | we'd create an openstack resource type, that loks like the contents of globals.yml. | 21:05 |
*** dwalsh has joined #openstack-kolla | 21:06 | |
kfox1111 | the operator would then be handed it, run genconfig, and launch containers with all the config bits generated from it. | 21:06 |
inc0 | which would basically be kolla-ansible that changes kolla_docker starting containers to kubectl | 21:06 |
kfox1111 | when the user wants to upgrade, they change the gloals to say, s/mitaka/ocata/ | 21:06 |
kfox1111 | the operator would see the change, run through an upgrade procedure on each of the containers/configs. | 21:07 |
inc0 | only inside pod | 21:07 |
kfox1111 | yeah, and driving k8s. | 21:07 |
inc0 | that's not as bad as it sounds, but meh, just sayin', operators = I'm not amused | 21:07 |
kfox1111 | yeah. its just a different way of doing the workflow stuff we've talked about adnosium. :) | 21:08 |
inc0 | yet another wheel | 21:08 |
v1k0d3n | so inc0 we just need a direction. sort of quickly from our pov. i think a lot of this is just unclear understanding of the operator and entrypoint differences. | 21:08 |
kfox1111 | it can be external to k8s with ansible/chef/whatever, | 21:08 |
rhallisey | inc0, heh :) | 21:08 |
kfox1111 | or can be done internal in k8s as an operator. | 21:08 |
v1k0d3n | remember, i was a huge supporter of entrypoint a couple weeks ago :) | 21:08 |
v1k0d3n | at the time, it was the fastest path. | 21:08 |
inc0 | v1k0d3n, so from my point of view....we're re-implementing workflow | 21:08 |
inc0 | inside a container | 21:08 |
kfox1111 | so, the really shortest path is to continue with the existing kolla-kube-ansible stuff. | 21:09 |
v1k0d3n | misunderstanding | 21:09 |
inc0 | we could do it outside of container | 21:09 |
*** fguillot has quit IRC | 21:09 | |
v1k0d3n | and that will break what we need | 21:09 |
v1k0d3n | and NO | 21:09 |
v1k0d3n | container needs to do it. | 21:09 |
kfox1111 | it can be run outside k8s, or can be crammed into a contianer and wrapped in an operater very esily. | 21:09 |
v1k0d3n | understanding of a cloud native app is huge | 21:09 |
kfox1111 | then both types of workflows can be evaluated. | 21:09 |
v1k0d3n | i think education is really important here. | 21:09 |
v1k0d3n | even evaluating each is going to stall what we need. | 21:09 |
kfox1111 | agreed. and this stuff is like a week old. | 21:09 |
kfox1111 | how do you know operators are the way to go now? | 21:10 |
v1k0d3n | ^^ i agree with that. | 21:10 |
v1k0d3n | kfox1111: this was the whole reason for coming to kubecon | 21:10 |
v1k0d3n | yes | 21:10 |
kfox1111 | we should figrure out an quick/easy way to evaluate several things. | 21:10 |
v1k0d3n | this is the theme | 21:10 |
kfox1111 | then pick the best. :) | 21:10 |
inc0 | so I will bet money on it that when somebody will start using etcd operator they'll find all the nice edge cases that happends in distributed systems | 21:10 |
v1k0d3n | i have a better plan guys. | 21:10 |
kfox1111 | I do think operators have a very compelling story behind them. | 21:10 |
v1k0d3n | one common theme here....... | 21:10 |
inc0 | race conditions during operations | 21:10 |
kfox1111 | its just really really young. | 21:11 |
inc0 | and stuff like that | 21:11 |
*** aric49 has joined #openstack-kolla | 21:11 | |
v1k0d3n | inc0: race conditions? | 21:11 |
rhallisey | agreed, we don't know the best path. Code hasn't been written and tested | 21:11 |
v1k0d3n | are we not limiting operators? | 21:11 |
v1k0d3n | cgroup limit them | 21:11 |
inc0 | when operator thinks it's already deployed but it isnt | 21:11 |
rhallisey | also the reference architecture for operators within openstack is non existent | 21:11 |
inc0 | you know what would be great? | 21:11 |
v1k0d3n | that's the point....logic is built in. | 21:11 |
rhallisey | not within | 21:11 |
v1k0d3n | it's binary, it's there or not | 21:11 |
inc0 | write a DLS dedicated for operators | 21:11 |
rhallisey | using operators for a complex app like openstack | 21:11 |
inc0 | DSL | 21:11 |
kfox1111 | inc0: I don't think its racy. there is one operator container running, getting the requested state. | 21:12 |
v1k0d3n | lot of misunderstanding | 21:12 |
v1k0d3n | i think we need to have meetings with coreos. | 21:12 |
v1k0d3n | this is pivitol | 21:12 |
inc0 | kfox1111, what of fail tolerance? you can store only so much state in k8s | 21:12 |
v1k0d3n | *pivotal | 21:12 |
kfox1111 | inc0: yeah, the idea of thirdparty resources are to extend k8s using k8s. | 21:12 |
v1k0d3n | if we deploy entrypoint because we "feel" it's better.... | 21:12 |
v1k0d3n | and rewrite ansible. | 21:12 |
v1k0d3n | and learn that operators are the way to go.... | 21:13 |
kfox1111 | so it stores its state in a k8s configmap or something if it needs to stave state, or rebuilds state by quering k8s on startup. | 21:13 |
inc0 | maybe what we need is cloud-native-container-native-k8s-running version of ansible | 21:13 |
rhallisey | I mean do you guy think operators are not it? Maybe we need to invent something else here | 21:13 |
kfox1111 | entrypoint is not an orchestration system. | 21:13 |
kfox1111 | itss just a way to block stuff. | 21:13 |
inc0 | nah, it's simple mechanism to avoid race conditions during deployment | 21:13 |
inc0 | really really easy stuff | 21:13 |
kfox1111 | I do think operators are likely a good path for implementing workflow. | 21:13 |
v1k0d3n | maybe what we need is cloud-native-container-native-k8s-running version of ansible = total contradiction fyi | 21:13 |
kfox1111 | I really do. | 21:14 |
inc0 | v1k0d3n, ansible as in workflow engine | 21:14 |
rhallisey | v1k0d3n, yes but that's not on their roadmap | 21:14 |
kfox1111 | operators though are about api more then anything. | 21:14 |
inc0 | "do thing, wait till thing is done, do another thing" | 21:14 |
kfox1111 | so language really doesn't matter. | 21:14 |
rhallisey | anything of the sort | 21:14 |
kfox1111 | python/go/ansible, all would work I think. | 21:14 |
v1k0d3n | kfox1111: exactly right | 21:14 |
v1k0d3n | API driven | 21:14 |
v1k0d3n | cloud native | 21:14 |
v1k0d3n | dynamically scheduled. | 21:14 |
kfox1111 | its basically the same contract k8s provides. | 21:15 |
v1k0d3n | ansible is not dynamically scheduled. | 21:15 |
v1k0d3n | that is human operator scheduled. | 21:15 |
inc0 | it can be;) | 21:15 |
kfox1111 | "give me a declarative definition of what you want, and k8s will make it happen" | 21:15 |
inc0 | like puppet | 21:15 |
rhallisey | could you say OpenStack is not though? | 21:15 |
kfox1111 | for operators, k8s is extended by an container running in the same k8s. | 21:15 |
inc0 | same thing;) | 21:15 |
inc0 | maybe puppet-k8s | 21:15 |
v1k0d3n | inc0: omg...smh | 21:15 |
inc0 | ? | 21:15 |
v1k0d3n | ok | 21:15 |
inc0 | v1k0d3n, let's have a hangout | 21:15 |
v1k0d3n | there's misunderstanding here. | 21:15 |
inc0 | with coreos guys | 21:15 |
kfox1111 | puppet-k8s would work too. language really really doesn't matter. | 21:16 |
inc0 | I'm sure there is | 21:16 |
v1k0d3n | i can't. meeting with CoreOS to talk about this very subject | 21:16 |
kfox1111 | whatevers the best tool for the job. | 21:16 |
v1k0d3n | i thought this would be so much easier. | 21:16 |
v1k0d3n | there's too much religion | 21:16 |
inc0 | v1k0d3n, I'm not *against* it | 21:16 |
inc0 | no religion involved | 21:16 |
inc0 | I might just misunderstand the idea | 21:16 |
rhallisey | v1k0d3n, this is a tough problem b/c openstack and kube interaction | 21:16 |
kfox1111 | v1k0d3n: i'm not against it either. nor religious about it. | 21:16 |
v1k0d3n | inc0: we're not moving forward. | 21:16 |
inc0 | totally possible | 21:16 |
v1k0d3n | days of discussion around this. | 21:16 |
inc0 | v1k0d3n, I want to know where we going before we move | 21:16 |
inc0 | days? it exists a week! | 21:17 |
rhallisey | I think we're moving forward with the spec and POCs happening | 21:17 |
inc0 | in total | 21:17 |
kfox1111 | v1k0d3n: no, I think its that most people really do't have a handle on operators yet. | 21:17 |
kfox1111 | so more of a push back from lack of understanding I think. | 21:17 |
kfox1111 | more education is needed. | 21:17 |
v1k0d3n | inc0: ....we're not using etcd exactly as is..... | 21:17 |
inc0 | v1k0d3n, how about you guys alongside with sdake write a poc of operator-driven deploy of mariadb+keystone | 21:17 |
v1k0d3n | this is a MODEL | 21:17 |
v1k0d3n | a show of how it should be done. | 21:17 |
v1k0d3n | this is just an architecture logic. | 21:17 |
v1k0d3n | differently explained. | 21:17 |
v1k0d3n | it's not out a week....the concept was there all along, just someone showed us a better path. | 21:18 |
inc0 | v1k0d3n, can you do that for me? | 21:18 |
v1k0d3n | it's an idea...not a technology. | 21:18 |
inc0 | regardless of language used | 21:18 |
kfox1111 | yeah. a phylosophy. | 21:18 |
inc0 | just deploy mariadb and keystone with it | 21:18 |
v1k0d3n | ^^ right | 21:18 |
kfox1111 | extend k8s with a container to allow the user to request a particular declarative object, and the operator drives k8s to make it realized. | 21:19 |
inc0 | and I get that, all I'm saying is workflow automation is hard problem | 21:19 |
inc0 | really hard | 21:19 |
v1k0d3n | so a comment like "it's only been out a week" is like finding water underground. it's always been there. | 21:19 |
kfox1111 | inc0: +1 | 21:19 |
inc0 | especially if we want distributed workflow automation | 21:19 |
*** neilus has quit IRC | 21:19 | |
kfox1111 | all around, I don't think this matters too much. | 21:19 |
kfox1111 | the workflow is the hard part. | 21:19 |
kfox1111 | whether its drivven by data fed through k8s thirdparty resources, | 21:19 |
v1k0d3n | i agree. | 21:19 |
inc0 | yeah, whether we put it inside container or not | 21:19 |
kfox1111 | or by the user directly, | 21:19 |
v1k0d3n | inc0: my whole point of coming in here is to get buyin.... | 21:20 |
kfox1111 | the logic is the hard part. | 21:20 |
v1k0d3n | listen for a sec. | 21:20 |
kfox1111 | the input format is easy. | 21:20 |
v1k0d3n | if you would agree to operator, i have more of a case with Alex at 1:30 | 21:20 |
v1k0d3n | to say, "we can explore this, can you help" | 21:20 |
v1k0d3n | if we have no path, i have nothing to say to him | 21:20 |
inc0 | and I'm not too keen in implementing this logic on programming language level | 21:20 |
v1k0d3n | zero leverate. | 21:20 |
v1k0d3n | leverage | 21:20 |
kfox1111 | I'm all for giving operators a shoit. I think they are a good thing on the face of it. | 21:20 |
kfox1111 | shot | 21:20 |
inc0 | v1k0d3n, say that we agree | 21:20 |
rhallisey | v1k0d3n, that's what we're doing (me and sdake) | 21:20 |
inc0 | and we'll deal with issues later | 21:20 |
rhallisey | v1k0d3n, tell him to read the spec | 21:21 |
inc0 | I'm just worried that we underestimate complexity of this thing | 21:21 |
v1k0d3n | let me find out from alex what they are doing with stackanetes and the forward path. | 21:21 |
kfox1111 | yeah. the spec lis looking pretty good. | 21:21 |
kfox1111 | inc0: thats a problem if workflow, not really operators. | 21:21 |
v1k0d3n | and if they say "we need operators" then what? | 21:21 |
kfox1111 | I think. | 21:21 |
v1k0d3n | they want to go back to kolla...this much i know | 21:21 |
kfox1111 | workflow itself is really hard/complicated. | 21:21 |
v1k0d3n | been said several times | 21:21 |
v1k0d3n | gotta run guys. close to time. | 21:21 |
inc0 | v1k0d3n, ok, if operators will get them back, greay | 21:21 |
kfox1111 | an operator is mostly just wrapping/syntactic sugar | 21:21 |
rhallisey | v1k0d3n, that's good. Let's start with the operator common ground and go form there | 21:21 |
inc0 | let's roll with this | 21:21 |
v1k0d3n | just wanted to share. | 21:21 |
v1k0d3n | let me find out. be back in a bit | 21:22 |
inc0 | again I'm not opposed, just this thing is really complex | 21:22 |
*** v1k0d3n has quit IRC | 21:22 | |
rhallisey | since we clearly don't know the final answer here | 21:22 |
rhallisey | we need to have some POCs | 21:22 |
inc0 | and I don't want to reinvent wheels | 21:22 |
inc0 | these are my only reservations | 21:22 |
rhallisey | inc0, I agree dude | 21:22 |
kfox1111 | inc0: +1 | 21:22 |
rhallisey | we need to find how this fits kube and OpenStack | 21:22 |
inc0 | I go to etcd controller and see golang code implementing workflow for deployment of single (complex) application | 21:23 |
rhallisey | I think we all believe it can, but the how is still WIP | 21:23 |
inc0 | I could very well implement it in python, but we didn't we used ansible already cuz ansible helps with certain stuff, like failure handling and whatnot | 21:23 |
rhallisey | inc0, ehh failure handling :), but poor error reporting | 21:24 |
inc0 | maybe what we need is clever way to implement stuff with operators without writing EVERYTHING from scratch | 21:24 |
kfox1111 | k8s itself helps alreayd with a lot of failure cases. | 21:24 |
inc0 | maybe that's a good idea for operator-centric project | 21:24 |
rhallisey | inc0, yes I agree, but I think the crux here is that operators are a good step | 21:24 |
srwilkers | really loving how active this chats been the past week | 21:24 |
rhallisey | imno | 21:24 |
inc0 | to write a DSL for it | 21:24 |
kfox1111 | mostly the operator is just driving k8s to do a few things. if we do it per service level, | 21:24 |
kfox1111 | its probably 5 or 6 steps max per operator. | 21:24 |
rhallisey | srwilkers, :) | 21:24 |
inc0 | ah, we lost Brandon | 21:25 |
inc0 | duh | 21:25 |
srwilkers | yeah, he had to jet | 21:25 |
inc0 | ok, on the bright note, http://paste.openstack.org/show/588612/ <- put this into globals.yml and it will include contents of file specified into playbook | 21:26 |
inc0 | ansible customizations \o/ | 21:26 |
inc0 | I got it almost working | 21:26 |
kfox1111 | nice. | 21:26 |
srwilkers | so rhallisey, you and sdake are working on the operator poc yeah? | 21:27 |
kfox1111 | we need to figure out how to do similar things with kolla-kubernetes too. | 21:27 |
inc0 | kfox1111, won't helm help with that? | 21:27 |
kfox1111 | some. | 21:27 |
kfox1111 | I'm more talking about genconfig ini file overrides. | 21:27 |
kfox1111 | there isn't an easy way to override some values currently I think. | 21:27 |
kfox1111 | I think kolla-ansible supports that, but I think it was doing it on the host using ansible, which doesn't work for kolla-kubernetes. | 21:28 |
*** psanchez has joined #openstack-kolla | 21:28 | |
sdake | wow lacks of scrollback | 21:29 |
kfox1111 | indeed | 21:29 |
sdake | lots | 21:29 |
sdake | autocorrect failure | 21:29 |
*** slagle has joined #openstack-kolla | 21:31 | |
sdake | hey slagle how goes it | 21:31 |
sdake | inc0 re clever way to implement stuff with controllers - thats with a base class that does everything\ | 21:32 |
sdake | i have thought about a dsl too, but that starts to infringe on ansible territory i think | 21:32 |
inc0 | what I'm saying is - we're reinventing wheel there, let's make sure it's nice and round | 21:33 |
kfox1111 | [A[B[B[B[B | 21:33 |
inc0 | tmux? | 21:33 |
kfox1111 | screen. :) | 21:33 |
kfox1111 | wifi partially died. | 21:33 |
*** Jeffrey4l has quit IRC | 21:34 | |
*** stevebaker has joined #openstack-kolla | 21:34 | |
kfox1111 | sdake: yeah. I think the vast majority of the services just "create mysql db, create keystone entries, start k8s deployment object" | 21:34 |
kfox1111 | so the code will mostly be the same for the operators. | 21:34 |
kfox1111 | the differences usualy are in the upgrade code. | 21:34 |
sdake | kfox1111 a wrapper only installs a command which does orchestration | 21:34 |
rhallisey | srwilkers, ya | 21:35 |
*** chas_ has joined #openstack-kolla | 21:35 | |
*** nihilifer has quit IRC | 21:36 | |
kfox1111 | sdake: yeah. I'm saying I think if we write a python operator for most of the base services, they can all inherit from a base class that does those actions and is basially just a sub to allow us to add upgrade logic specific to the service later. | 21:37 |
*** fguillot has joined #openstack-kolla | 21:38 | |
inc0 | ehh | 21:38 |
inc0 | I think this whole model is overhyped | 21:38 |
inc0 | this is just a fucking script that does stuff | 21:38 |
inc0 | no matter how you call it | 21:39 |
kfox1111 | inc0: overhyhed/under-understood, but still good. | 21:39 |
inc0 | as good as script written | 21:39 |
kfox1111 | it just makes it such that you can kubectl create -f mycloud.yaml | 21:39 |
kfox1111 | intead of calling pythonscript mycloud.yaml | 21:39 |
inc0 | yeah | 21:39 |
inc0 | pretty much | 21:39 |
inc0 | make shipping easier | 21:39 |
*** ayoung has joined #openstack-kolla | 21:40 | |
kfox1111 | yeah. | 21:40 |
kfox1111 | as you can: | 21:40 |
kfox1111 | helm install kolla-operator | 21:40 |
kfox1111 | kubectl create -f mycloud.yaml | 21:40 |
kfox1111 | profit. :) | 21:40 |
*** chas_ has quit IRC | 21:40 | |
kfox1111 | no non k8s stuff needed installed. | 21:40 |
inc0 | just this script in python will be fuckton of work to make it well | 21:40 |
kfox1111 | could be. | 21:40 |
pron | emm i belive we have an error here http://docs.openstack.org/developer/kolla/multinode.html | 21:41 |
inc0 | with infinite resources every model is a good one | 21:41 |
kfox1111 | but in an operator or in a stand alone script, thats the same work either way. | 21:41 |
inc0 | whats that pron ? | 21:41 |
pron | MountFlags=shared missing in ubuntu service file | 21:41 |
pron | i think at least , since i am trying to play with kolla atm | 21:42 |
*** aric49 has quit IRC | 21:42 | |
inc0 | you're right | 21:42 |
*** aric49 has joined #openstack-kolla | 21:42 | |
inc0 | wanna make a fix?:)P | 21:42 |
*** aric49 has quit IRC | 21:42 | |
sdake | kfox1111 know much about python? | 21:43 |
sdake | thats the base class i was speaking of ;) | 21:44 |
*** nihilifer has joined #openstack-kolla | 21:44 | |
* pron hides | 21:44 | |
inc0 | still, fuckton of work to make it correctly | 21:44 |
srwilkers | inc0, pron: i can fix it right quick if you dont want to | 21:45 |
pron | lets make i deal , i dont do fixes but report stuff here :P most likely a lot since our plan is to use kolla :P | 21:45 |
sdake | i'd admit makign upgrade work correctly will be work | 21:45 |
pron | make a deal* | 21:45 |
sdake | deploy will be easy | 21:45 |
sdake | pron file bugs :) | 21:46 |
inc0 | pron, sure, any help is appreciated | 21:46 |
pron | well ;D i will find a ways to break stuff | 21:46 |
inc0 | tha'ts core reviewers issue to spot | 21:46 |
rhallisey | sdake, ya doing the entire life cycle amplifies the problem | 21:46 |
inc0 | don't worry, it's not that easy to break stuff pron | 21:46 |
inc0 | but it is cool feeling when you contribute | 21:46 |
pron | hehe lets see i alrdy spent some time with weird stuff that i wasnt avare of :P | 21:46 |
pron | first of all i am tryign to do that in mirantis os deployment :D | 21:47 |
inc0 | anyway, I'd encourage you to try | 21:47 |
inc0 | like...deploy OS with nailgun or ...? | 21:47 |
inc0 | sdake, no, it won't be that easy | 21:47 |
inc0 | even deploy | 21:47 |
pron | nono i have tht mirantis thing deployed for well the sake of having it before i vent to barceolna | 21:47 |
inc0 | remember compose? | 21:48 |
inc0 | think if this shellscript we used as operator | 21:48 |
inc0 | put it into container | 21:48 |
sdake | burned into my brian | 21:48 |
inc0 | and tha'ts it | 21:48 |
srwilkers | im sure brian doesnt appreciate that sdake | 21:48 |
inc0 | 19 out of 20 times it works | 21:48 |
pron | anyways i like that bugs are welcomed here :P so i will bring em if i spot something | 21:48 |
sdake | srwilkers nope | 21:48 |
inc0 | thanks pron | 21:48 |
sdake | pron our bug triage is a little laggy | 21:48 |
sdake | pron so if somethign critical comes up feel free to point it out | 21:49 |
*** harlowja has joined #openstack-kolla | 21:49 | |
sdake | pron however the common services rae in rock solid shape | 21:49 |
pron | well at least i am not turned away :P list most projects newdays do | 21:49 |
pron | like* ( sorry i type liek dislectic ) | 21:49 |
inc0 | nah, bugs are greatly appreciated and we thank you for them | 21:49 |
*** huikang has quit IRC | 21:50 | |
inc0 | just in certain cases making a patchset with fix takes even less time;) | 21:50 |
*** huikang has joined #openstack-kolla | 21:50 | |
*** mgiles has quit IRC | 21:52 | |
*** huikang has quit IRC | 21:54 | |
*** jheroux has quit IRC | 22:04 | |
kfox1111 | sry. back. | 22:05 |
*** msimonin has joined #openstack-kolla | 22:05 | |
*** msimonin1 has quit IRC | 22:06 | |
kfox1111 | inc0: compose is too single minded/static. | 22:06 |
kfox1111 | k8s behaves quite a bit differently. | 22:06 |
kfox1111 | so it will probably be a different set of issues. :) | 22:07 |
*** huikang has joined #openstack-kolla | 22:07 | |
inc0 | I know, we actually have source to query state of things | 22:07 |
*** fguillot has quit IRC | 22:07 | |
*** sdake has quit IRC | 22:09 | |
kfox1111 | :) | 22:12 |
kfox1111 | stupid kubeadm preflight checks... :/ | 22:13 |
openstackgerrit | Kevin Fox proposed openstack/kolla-kubernetes: Fix new kubeadm precheck https://review.openstack.org/395779 | 22:14 |
*** lrensing has quit IRC | 22:15 | |
openstackgerrit | Michal Jastrzebski (inc0) proposed openstack/kolla: DO NOT MERGE!: PoC of ansible override https://review.openstack.org/395851 | 22:22 |
*** schwicht has quit IRC | 22:23 | |
openstackgerrit | Michal Jastrzebski (inc0) proposed openstack/kolla: DO NOT MERGE!: PoC of ansible override https://review.openstack.org/395851 | 22:24 |
*** neilus has joined #openstack-kolla | 22:25 | |
openstackgerrit | Kevin Fox proposed openstack/kolla-kubernetes: Fix new kubeadm precheck https://review.openstack.org/395779 | 22:29 |
*** n3v3rm0r3r has joined #openstack-kolla | 22:29 | |
*** berendt has quit IRC | 22:36 | |
*** chas_ has joined #openstack-kolla | 22:36 | |
*** chas_ has quit IRC | 22:41 | |
*** schwicht has joined #openstack-kolla | 22:45 | |
*** rhallisey has quit IRC | 22:48 | |
*** dwalsh has quit IRC | 22:51 | |
*** dwalsh has joined #openstack-kolla | 22:52 | |
*** dwalsh has quit IRC | 22:57 | |
*** tonanhngo has quit IRC | 22:57 | |
openstackgerrit | OpenStack Proposal Bot proposed openstack/kolla: Updated from global requirements https://review.openstack.org/395324 | 22:57 |
*** schwicht has quit IRC | 22:58 | |
*** dwalsh has joined #openstack-kolla | 22:58 | |
openstackgerrit | Kevin Fox proposed openstack/kolla-kubernetes: Fix new kubeadm precheck https://review.openstack.org/395779 | 22:59 |
*** Pavo has joined #openstack-kolla | 23:01 | |
*** schwicht has joined #openstack-kolla | 23:02 | |
*** neilus has quit IRC | 23:08 | |
*** neilus has joined #openstack-kolla | 23:08 | |
*** harlowja_ has joined #openstack-kolla | 23:08 | |
openstackgerrit | Steve Wilkerson proposed openstack/kolla: Added MountFlags for Ubuntu in multinode guide https://review.openstack.org/395865 | 23:08 |
*** sdake has joined #openstack-kolla | 23:09 | |
*** harlowja has quit IRC | 23:12 | |
*** schwicht has quit IRC | 23:12 | |
*** msimonin has quit IRC | 23:14 | |
*** alteriks has quit IRC | 23:15 | |
*** saneax-_-|AFK is now known as saneax | 23:15 | |
*** f13o has quit IRC | 23:16 | |
*** ayoung has quit IRC | 23:16 | |
*** huikang has quit IRC | 23:16 | |
*** huikang has joined #openstack-kolla | 23:17 | |
*** tonanhngo has joined #openstack-kolla | 23:17 | |
*** alteriks has joined #openstack-kolla | 23:19 | |
*** TxGirlGeek has quit IRC | 23:21 | |
*** huikang has quit IRC | 23:21 | |
*** tonanhngo has quit IRC | 23:22 | |
*** ayoung has joined #openstack-kolla | 23:28 | |
kfox1111 | sdake: alive? | 23:31 |
sdake | wound me kfox1111 | 23:31 |
*** Jeffrey4l has joined #openstack-kolla | 23:31 | |
kfox1111 | what was the etherpad url you give me to put helm stuff in? | 23:31 |
kfox1111 | I came up with another one. | 23:31 |
Pavo | evening | 23:31 |
*** Jeffrey4l has quit IRC | 23:32 | |
Pavo | question | 23:32 |
*** Jeffrey4l has joined #openstack-kolla | 23:32 | |
Pavo | if I am using Ceph on both Controller and Compute nodes, why would Horizon only show the Compute node amount and not both | 23:32 |
*** dwalsh has quit IRC | 23:33 | |
*** Jeffrey4l has quit IRC | 23:33 | |
sdake | kfox1111 no idea | 23:34 |
*** msimonin has joined #openstack-kolla | 23:34 | |
*** Jeffrey4l has joined #openstack-kolla | 23:34 | |
kfox1111 | was one of the summit ones I think. | 23:36 |
*** jrich523 has quit IRC | 23:37 | |
kfox1111 | found it. https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-road-map | 23:37 |
inc0 | sdake, https://review.openstack.org/#/c/395851/2 | 23:39 |
kfox1111 | sdake: can you read hte last bullet there and see if it makes sense? | 23:40 |
*** tonanhngo has joined #openstack-kolla | 23:41 | |
*** lamt has quit IRC | 23:42 | |
*** jrich523 has joined #openstack-kolla | 23:44 | |
jascott1 | im using kolla keystone image with helm, (openstack-helm uses their own custom images) and I am just trying to get the keystone container up | 23:45 |
jascott1 | I see this env var KOLLA_BASE_DISTRO=ubuntu | 23:45 |
jascott1 | but when i let the container do its bootup, it fails trying to start httpd | 23:45 |
jascott1 | which should only occur on non-debian | 23:45 |
jascott1 | does it not use KOLLA_BASE_DISTRO=ubuntu env var? | 23:45 |
openstackgerrit | Kevin Fox proposed openstack/kolla-kubernetes: Fix new kubeadm precheck https://review.openstack.org/395779 | 23:46 |
kfox1111 | I'm guessing that comes from /etc/kolla/horizon/config.json | 23:48 |
kfox1111 | or however your mapping that in. | 23:48 |
kfox1111 | not sure the env var does anything for that? | 23:49 |
jascott1 | hmm i will check there thx | 23:49 |
kfox1111 | actually, | 23:50 |
kfox1111 | there is code in /usr/local/bin/kolla_extend_start inside the container that seems to use it. | 23:50 |
*** tonanhngo has quit IRC | 23:50 | |
jascott1 | ya config.json just says which config files to copy and what perms to set | 23:50 |
kfox1111 | plus what command to execute. | 23:51 |
kfox1111 | so has an httpd command. | 23:51 |
kfox1111 | not sure that varies on ubuntu/centos though. | 23:51 |
kfox1111 | I know debian renames their stuff apache2 | 23:51 |
*** inc0 has quit IRC | 23:52 | |
jascott1 | im going to petition new pres to require all containers to include vim-tiny ;) | 23:52 |
jascott1 | ya that script looks like it just pulls from env... not sure whats going on | 23:53 |
srwilkers | yes pls | 23:53 |
kfox1111 | yeah. I'm having a hell of a time transitioning to a vi world from vim. | 23:54 |
jascott1 | you can actually mount vim tiny as volume, used to do that w docker | 23:54 |
kfox1111 | I want vim when I type vi if its installed, but that half the time works and half not. :/ | 23:54 |
kfox1111 | so just typing vi doesnt' always get me what I want. :/ | 23:54 |
kfox1111 | I've asked k8s to provide something sligtly different. | 23:54 |
jascott1 | yeah I always type vi | 23:55 |
kfox1111 | what I want, is an extension of the sidecar idea. | 23:55 |
kfox1111 | a toolbox sidecar. | 23:55 |
jascott1 | not familiar tho I have seen that term around | 23:55 |
kfox1111 | then you attach the sidecar, get a shell from the sidecar, with vim, gdb, strace, tcpdump ,etc | 23:55 |
kfox1111 | and but the filesystem would be from the container your debugging. :) | 23:55 |
*** tonanhngo has joined #openstack-kolla | 23:55 | |
jascott1 | ah cool | 23:55 |
kfox1111 | so you could keep your main containers really thin :) | 23:56 |
srwilkers | thats actually pretty great | 23:56 |
jascott1 | without exposing the filesystem from main conainer to the sidecar manually I suppose | 23:56 |
kfox1111 | yeah. | 23:56 |
*** chas_ has joined #openstack-kolla | 23:56 | |
kfox1111 | would be super useful. | 23:56 |
kfox1111 | each admin could even then have their own custom toolbox. and when detached, it just vanishes. :) | 23:56 |
kfox1111 | someone totally needs to implement that. :) | 23:57 |
jascott1 | sounds like everyone would like it | 23:57 |
kfox1111 | pile on: https://github.com/kubernetes/kubernetes/issues/27464 :) | 23:59 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!