Sunday, 2016-11-06

*** tonanhngo has quit IRC00:04
openstackgerritWei Cao proposed openstack/kolla: Add header blocks in CONTRIBUTING.rst guide  https://review.openstack.org/39395900:25
*** saneax-_-|AFK is now known as saneax00:29
Pavohttps://www.youtube.com/watch?v=dXMfdpjnAHU00:31
Pavoopps00:31
openstackgerritWei Cao proposed openstack/kolla: remove fedora support  https://review.openstack.org/39407400:37
*** saneax is now known as saneax-_-|AFK00:40
*** caowei has joined #openstack-kolla00:41
*** dwalsh has joined #openstack-kolla00:55
*** dave-mccowan has joined #openstack-kolla01:10
*** srwilkers has joined #openstack-kolla01:18
*** dave-mccowan has quit IRC01:23
*** neilus has joined #openstack-kolla01:26
*** neilus has quit IRC01:30
*** srwilkers has quit IRC01:40
*** huikang has quit IRC01:44
*** huikang has joined #openstack-kolla01:44
*** srwilkers has joined #openstack-kolla01:48
*** srwilkers has left #openstack-kolla01:48
*** huikang has quit IRC01:49
*** dwalsh has quit IRC01:57
*** huikang has joined #openstack-kolla02:09
*** bmace_ has quit IRC02:12
*** bmace_ has joined #openstack-kolla02:13
*** huikang has quit IRC02:20
*** huikang has joined #openstack-kolla02:40
*** haplo37 has quit IRC02:48
*** g3ek has quit IRC02:48
*** g3ek has joined #openstack-kolla02:54
*** haplo37 has joined #openstack-kolla02:55
openstackgerritWei Cao proposed openstack/kolla: Add freezer container  https://review.openstack.org/37490803:12
openstackgerritWei Cao proposed openstack/kolla: Add freezer ansible role  https://review.openstack.org/37587403:57
openstackgerritMerged openstack/kolla: when condition corrected in ceilometer config.yml  https://review.openstack.org/39406704:04
openstackgerritMerged openstack/kolla: baremetal group defined in all-in-one  https://review.openstack.org/39383204:19
openstackgerritMerged openstack/kolla: Add header blocks to Dockerfiles  https://review.openstack.org/39395504:20
*** sdake has joined #openstack-kolla04:35
openstackgerritWei Cao proposed openstack/kolla: Add solum ansible role  https://review.openstack.org/35893804:38
openstackgerritMerged openstack/kolla: Remove hostname from 127.0.0.1  https://review.openstack.org/38872204:42
openstackgerritprameswar proposed openstack/kolla: Custom policy files  https://review.openstack.org/39414704:44
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723204:46
openstackgerritJeffrey Zhang proposed openstack/kolla: Use openstack_service_workers variable in gate  https://review.openstack.org/39414804:49
openstackgerritprameswar proposed openstack/kolla: when condition corrected in ceilometer config.yml  https://review.openstack.org/39414904:49
openstackgerritMerged openstack/kolla: Remove inputs.filestat from telegraf configuration  https://review.openstack.org/38793504:58
openstackgerritMerged openstack/kolla: Include oslo.vmware along with other oslo packages in openstack-base.  https://review.openstack.org/39374404:59
openstackgerritJeffrey Zhang proposed openstack/kolla: Install all python packages in global-requirements.txt file  https://review.openstack.org/39415005:04
sdakelots o patches05:07
sdakeevening folks05:07
*** huikang has quit IRC05:07
sdakedoes this channel ever sleep ;)05:07
*** Jeffrey4l has joined #openstack-kolla05:13
openstackgerritMerged openstack/kolla: Add reconfigure.yml for bifrost  https://review.openstack.org/39088005:18
sdakeJeffrey4l did you see my emial re the repo split05:24
* Jeffrey4l is reading sdake 05:25
sdakethe tldr is I may need a little help ;)05:25
sdake(on project-config)05:25
sdakeI'll start the work on the 10th when i return from travel05:26
Jeffrey4lgate fix should be the hardest, ino05:26
Jeffrey4limo05:26
sdakeagree05:26
sdakei was hoping we cant ackle it together05:27
Jeffrey4lnp05:27
sdakeafter i get through the rigamarlole required by the repo split05:27
sdakenot that i don't thikn others could do the job, but if we could just wait until the 10th when i return, I will get cracking05:28
sdakebecause the repo additions in particular are tricky05:28
sdakenot hard, just tricky05:28
Jeffrey4li do not think other guys is working this expect u. ;)05:28
Jeffrey4lyep. git history.05:28
sdakedo you mean others expect me to tackle this?05:29
sdake(your sentence didn't parse for me)05:29
Jeffrey4li mean other guys is not working on repo split.05:29
Jeffrey4lbtw, i can take the work of fixing gate jobs. ;)05:30
sdakecool - i will help05:37
sdakei want to get back into dev more05:37
sdakespecificially around kolla-kubernetes05:37
sdakebut job needs to be finished on repo split first05:38
sdakeptl is sort of an engineering management job of a project as busy as kolla05:38
sdakefeel a bit like i'm out of the tech05:38
sdakewhereas I used to write half the commits to the repo05:38
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723205:45
openstackgerritMerged openstack/kolla: Fix broken test in vagrant boostrap script  https://review.openstack.org/38926606:00
openstackgerritMerged openstack/kolla: nova-spicehtml5proxy dependency package added  https://review.openstack.org/39289606:00
*** sdake_ has joined #openstack-kolla06:05
*** sdake has quit IRC06:05
*** sdake has joined #openstack-kolla06:07
*** sdake_ has quit IRC06:10
openstackgerritprameswar proposed openstack/kolla: nova-spicehtml5proxy dependency package added  https://review.openstack.org/39415106:14
openstackgerritJeffrey Zhang proposed openstack/kolla: Make service_checks easier to run independently of kolla-ansible  https://review.openstack.org/38116106:16
openstackgerritMerged openstack/kolla: Fix plugin parsing for base images  https://review.openstack.org/39329106:16
openstackgerritPraveen N proposed openstack/kolla: fix magnum [keystone_authtoken] configuration  https://review.openstack.org/38830506:36
openstackgerritJeffrey Zhang proposed openstack/kolla: Adding logrotate configuration for ceilometer  https://review.openstack.org/38971006:40
openstackgerritJeffrey Zhang proposed openstack/kolla: Check api_interface instead of network_interface  https://review.openstack.org/38665406:43
*** tonanhngo has joined #openstack-kolla06:44
openstackgerritMerged openstack/kolla: Add upgrade.yml for bifrost  https://review.openstack.org/39086306:45
openstackgerritJeffrey Zhang proposed openstack/kolla: Deploy Telegraf on all nodes  https://review.openstack.org/38888506:55
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723207:17
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723207:23
*** csj has joined #openstack-kolla07:29
openstackgerritprameswar proposed openstack/kolla: disable firewall in bootstrap-server  https://review.openstack.org/39310207:30
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723207:32
*** tonanhngo has quit IRC07:35
*** csj has quit IRC07:39
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723207:45
*** csj has joined #openstack-kolla07:58
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723207:59
*** sdake has quit IRC08:08
*** csj has quit IRC08:10
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723208:11
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723208:16
openstackgerritzhubingbing proposed openstack/kolla: add panko dockerfile  https://review.openstack.org/38723208:25
*** saneax-_-|AFK is now known as saneax08:52
*** saneax is now known as saneax-_-|AFK09:03
*** dwalsh has joined #openstack-kolla09:52
*** dwalsh has quit IRC10:01
*** caowei has quit IRC11:41
openstackgerritEduardo Gonzalez proposed openstack/kolla: Add custom policies in service.json  https://review.openstack.org/39417712:46
openstackgerritEduardo Gonzalez proposed openstack/kolla: Add custom policies in service.json  https://review.openstack.org/39417712:48
openstackgerritJeffrey Zhang proposed openstack/kolla: Uses tunnel_interface as ovs tunnel instead of api_interface  https://review.openstack.org/39209412:51
*** neilus has joined #openstack-kolla12:53
openstackgerritJeffrey Zhang proposed openstack/kolla: remove override_install_langs option in /etc/yum.conf  https://review.openstack.org/39163112:57
openstackgerritJeffrey Zhang proposed openstack/kolla: Configure log path for kibana  https://review.openstack.org/39417813:01
openstackgerritJeffrey Zhang proposed openstack/kolla: updates sources.list and apt prefereses filename to match dockerfile.  https://review.openstack.org/38659213:06
openstackgerritJeffrey Zhang proposed openstack/kolla: Allow flexibility in mysql backend for ceilometer  https://review.openstack.org/39211113:08
*** Jeffrey4l has quit IRC13:19
*** neilus has quit IRC13:21
*** neilus has joined #openstack-kolla13:50
*** neilus has quit IRC13:55
Pavomorning14:00
*** srwilkers has joined #openstack-kolla14:15
*** dwalsh has joined #openstack-kolla14:39
*** neilus has joined #openstack-kolla14:45
*** neilus has quit IRC14:46
*** neilus has joined #openstack-kolla14:47
*** dwalsh has quit IRC14:56
*** srwilkers has quit IRC15:06
*** srwilkers has joined #openstack-kolla15:07
*** csj has joined #openstack-kolla15:32
csjhi, I use kolla+vagrant to install a AIO. as the document mentioned `source ~/openrc`, I don't find this file in my operator kvm :(15:33
csjdoc is here: http://docs.openstack.org/developer/kolla/devenv-vagrant.html15:34
openstackgerritEduardo Gonzalez proposed openstack/kolla: Horizon custom policies  https://review.openstack.org/39418715:47
*** sdake has joined #openstack-kolla16:31
*** Pavo has quit IRC16:45
*** Pavo has joined #openstack-kolla16:49
*** v1k0d3n has joined #openstack-kolla16:50
*** g3ek has quit IRC16:52
*** haplo37 has quit IRC16:53
*** haplo37 has joined #openstack-kolla16:53
*** g3ek has joined #openstack-kolla16:54
*** matrohon has joined #openstack-kolla17:21
*** srwilkers has quit IRC17:35
*** matrohon has quit IRC18:02
*** neilus has quit IRC18:07
*** bmace_ has quit IRC18:13
*** HyperJohnGraham has joined #openstack-kolla18:22
*** sdake has quit IRC18:34
*** neilus has joined #openstack-kolla18:37
*** neilus has quit IRC18:39
*** dave-mccowan has joined #openstack-kolla18:42
*** sdake has joined #openstack-kolla18:44
sdakehey peeps18:47
*** dave-mccowan has quit IRC18:48
openstackgerritMerged openstack/kolla: nova-spicehtml5proxy dependency package added  https://review.openstack.org/39415119:30
openstackgerritSteven Dake proposed openstack/kolla: Fix typo in doc/bifrost.rst  https://review.openstack.org/39262519:48
openstackgerritMerged openstack/kolla: Fix typo in doc/bifrost.rst  https://review.openstack.org/39262519:51
openstackgerritSteven Dake proposed openstack/kolla: remove override_install_langs option in /etc/yum.conf  https://review.openstack.org/39420019:52
openstackgerritMerged openstack/kolla: remove override_install_langs option in /etc/yum.conf  https://review.openstack.org/39163119:54
*** jtriley has joined #openstack-kolla20:03
openstackgerritMerged openstack/kolla: Allow flexibility in mysql backend for ceilometer  https://review.openstack.org/39211120:04
openstackgerritMerged openstack/kolla: Adding logrotate configuration for ceilometer  https://review.openstack.org/38971020:04
openstackgerritMerged openstack/kolla: Remove haproxy_socket volume from telegraf container  https://review.openstack.org/38763920:11
*** jtriley has quit IRC20:13
*** matrohon has joined #openstack-kolla20:19
Pavosup sdake20:23
sdakeyo pavo20:23
Pavohows it been20:23
sdakei've been looking into that problem related to fips-140 for you20:23
Pavoawesome20:23
sdakethe short answer is we use a library called pycrypto20:24
sdakei don't yet know if this library is fips-140 compliant, but the general belief on the ml is it is not20:24
Pavoas long as there nothing that md5 hashes its fine20:24
sdakewe dont use md5 in our code - but pycrypto implements md5 i suspect20:24
Pavoneeds to be atleast sha-25620:24
sdakemd5 is insecure as you probably are aware20:25
Pavoyeap20:25
Pavoso I have been playing around with custom ini files20:25
Pavocan't seem to get it working20:25
Pavoguess I am just doing it wrong20:25
sdakepossible20:25
sdaketell me what your doing20:25
PavoI created a folder in /etc/kolla named config20:26
Pavoinside that folder I have a neutron-server folder and inside that folder I have a ml2.conf.ini20:26
PavoI mean ml2_conf.ini20:26
PavoI added tenant_network_types = vxlan, vlan under [ml2] section and did a kolla-ansible reconfigure20:27
Pavochecked the new deployment, nothing changed20:27
Pavoso either I am not understanding the custom ini files or configured the folders wrongly20:28
Pavodunno20:28
Pavothere are a few changes I have to have customized for our environment and normally changed them in their respective ini files, like ml2 and dhcp_agent and horizon-dashboard.ini20:30
Pavobut for the life of me can not figure how to change them with kolla20:30
openstackgerritMerged openstack/kolla: Add profile usage to kolla-build guide  https://review.openstack.org/37823020:39
sdakepavo sorry i got mixed up in some work :)20:40
Pavono problem20:40
openstackgerritMerged openstack/kolla: Adjust object-replicator heading within object.conf.j2 template.  https://review.openstack.org/39152120:40
sdakepavo rename neutron-server to ust neutron i think20:40
sdakepavo also i can't guarantee that ml2 reconfiguration works - it should but i have never personally tested going rom vlan to vxlan or visa-versas20:41
openstackgerritSteven Dake proposed openstack/kolla: Adjust object-replicator heading within object.conf.j2 template.  https://review.openstack.org/39420320:41
Pavoyeah I am not going from to, I am just adding to have more options20:42
Pavobut I will try just using neutron as the folder name20:42
sdakeya so for top level services our model is config/nova/nova.conf not /config/nova/nova-conductor/nova.conf20:45
sdakewe used to have the second convention, but IIRC it was removed.20:45
Pavoin the source code, where is the code that looks for theses ini files?20:46
Pavobecause there has to be a list of what kolla will except and what it will not except20:46
Pavobecause its really hard to know what ini file to change with there being the same ini file for multiple containers20:48
*** srwilkers has joined #openstack-kolla20:55
openstackgerritSteven Dake proposed openstack/kolla: Adding logrotate configuration for ceilometer  https://review.openstack.org/39420420:56
sdakepavo moment20:56
sdakepavo https://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/config.yml#L51-L5720:57
Pavoso its located in the roles folder for every service?20:58
Pavook well changing it from neutron-server to just neutron worked21:00
Pavothis is going to be VERY tedious task to narrow down which ini files I need to customize21:00
Pavosdake take a look at this http://ddi.hopto.org:3000/henry.brock/OpenstackDDI/src/master/config/install.sh this is all the settings I use with packstack, which set the settings in the ini files for said service21:02
sdakepavo one option you ahve is just to copy your ini files over21:02
Pavothere are a ton that doesn't reflect what kolla names them as, so it going to take some time to figure which ones kolla names them as to customize21:02
*** jtriley has joined #openstack-kolla21:02
sdakepavo without doing a three way diff :)21:03
Pavotrue21:03
sdakeits not "optimal' but should get you going21:03
Pavoyeah21:04
openstackgerritMerged openstack/kolla: Add freezer container  https://review.openstack.org/37490821:07
*** jtriley has quit IRC21:07
*** jtriley has joined #openstack-kolla21:08
openstackgerritMerged openstack/kolla: Add header blocks in CONTRIBUTING.rst guide  https://review.openstack.org/39395921:08
*** neilus has joined #openstack-kolla21:11
*** jtriley has quit IRC21:13
*** dave-mccowan has joined #openstack-kolla21:23
openstackgerritMerged openstack/kolla: Mariadb performance tuning  https://review.openstack.org/38613021:26
*** haplo37 has quit IRC21:39
*** g3ek has quit IRC21:41
*** g3ek has joined #openstack-kolla21:42
*** haplo37 has joined #openstack-kolla21:46
openstackgerritMerged openstack/kolla: Add file validator for *.json.j2 file  https://review.openstack.org/38885121:47
*** v1k0d3n has quit IRC21:47
*** v1k0d3n has joined #openstack-kolla21:48
openstackgerritSteven Dake proposed openstack/kolla: Add file validator for *.json.j2 file  https://review.openstack.org/39420621:50
sdakesup v1k0d3n21:50
*** v1k0d3n has quit IRC21:51
*** v1k0d3n has joined #openstack-kolla21:51
v1k0d3nhey sdake what's up man21:52
v1k0d3nwhen are you taking off for kubecon?21:52
sdake3pm - arrive 5pm21:56
*** dave-mcc_ has joined #openstack-kolla22:04
*** dave-mccowan has quit IRC22:06
*** jtriley has joined #openstack-kolla22:09
*** matrohon has quit IRC22:10
*** dave-mccowan has joined #openstack-kolla22:13
*** jtriley has quit IRC22:14
sdakev1k0d3n if you are not aware, we are splitting the repositories of kolla into 322:14
sdakehttps://www.gliffy.com/go/publish/1133812522:14
sdakethere is a diagram, process that and tell me what you think22:15
sdakehave you had an opportunity to check out ryan's helm spec?22:15
sdakein ryan's spec, there is some discussion of using entrypoint project22:16
sdakehowever, this is problematic I htink because entrypoint provides its own JSON API model22:16
*** dave-mcc_ has quit IRC22:17
sdakeand we already have an API model in Kolla22:17
*** dave-mccowan has quit IRC22:17
sdakemaking these two inconsistent models work well together seems troubling to me22:17
*** neilus has quit IRC22:21
*** v1k0d3n has quit IRC22:30
*** v1k0d3n has joined #openstack-kolla22:35
*** v1k0d3n has quit IRC22:38
*** v1k0d3n has joined #openstack-kolla22:38
*** neilus has joined #openstack-kolla22:39
v1k0d3nnot sure how to correct the API issue, just know that having a self-contained, controller/operator model makes the solution cloud native.22:40
v1k0d3nnot sure if current isn't exactly cloud-native, but having a watchdog is what we're going to be after eventually.22:41
v1k0d3neven entrypoint will eventually turn into that operator model like: https://coreos.com/blog/introducing-the-etcd-operator.html22:41
v1k0d3nentrypoint is most likely a precursor to a much bigger movement, which seems to be supported by others from what i can tell.22:42
v1k0d3nsdake: ^^22:43
*** neilus has quit IRC22:44
sdakeother people that have tried that model didn't like it22:44
sdakeit works 95% of the time22:44
sdake5% of the time is fails.22:45
sdakewe tried heavily during compose work22:45
sdakeand asalkeld and co tried again with mesos22:45
sdakea completely decentralized model of self-orchestration22:45
sdakeso looking at  the etcd-oeprator github i see this:22:46
sdakeThe controller collects anonymous usage statistics to help us learning how the software is being used and how we can improve it. To disbale collection, run the controller with the flag -analytics=false22:46
sdakegroan...22:46
sdakehttps://github.com/coreos/etcd-operator22:46
sdakethe etcd operator is only for etcd22:47
sdakesounds like whta we really need is a kolla-operator22:47
sdakeas in rework kolla_start.sh into kolla_start_operator.sh22:47
sdakebut again it didn't work in the past ;)22:47
sdaketwo separate time22:48
*** dave-mccowan has joined #openstack-kolla22:51
sdakes22:55
sdakev1k0d3n are you napping at the keyboard again ;)22:56
sdakev1k0d3n that etcd_operator tool is written by two cats22:58
sdakehttps://github.com/coreos/etcd-operator/graphs/contributors22:58
sdakewhile that particular implementation looks appealing, i'd like to see something a little more resilient to busses22:58
sdake(noting it  only works for etcd:)22:59
v1k0d3nyeah, from what i've been discussing with a lot of folks...the ultimate goal would be to have app-specific operators.23:00
v1k0d3nfor each specific app logic.23:00
sdakecool23:00
sdakeso have you seen this? https://github.com/stackanetes/kubernetes-entrypoint23:00
v1k0d3nand really only for things that aren't cloud-native to start. galera/maria, rabbitmq, memcache, etc. for our purposes if it would be considered.23:00
v1k0d3nyeah, that's what i've been talking about over the past couple of weeks23:01
sdakedefine cloud native for me please23:01
v1k0d3n(operator was just "released" this past week).23:01
sdakethis is the api to that code base: https://github.com/stackanetes/stackanetes/blob/master/nova/manifest.jsonnet23:01
sdakeya probably a private repo then23:01
sdakei guess i saw "July" as the start point but if it was a private repo, then i'd see why it only has two authors23:02
v1k0d3ncontainer, dynamically scheduled, microservice in nature.23:02
v1k0d3nthe rub is in the dynamically scheduled...because if it's in "any old order" things like galera, rabbit...those aren't reliable anymore working with other applications.23:02
*** jtriley has joined #openstack-kolla23:03
v1k0d3nit was private. this was just release this past tuesday or wedsnesday maybe?23:03
sdakecould you back that with an argument :)23:03
v1k0d3nin what way do you mean?23:03
sdake"aren't reliable anymore"23:03
sdakeor facts23:04
sdakeor something rather then speculation ;)23:04
sdakenot that rabbitmq was all that reliable to begin with23:04
v1k0d3nok, so i want to upgrade newton to ocata....23:04
sdakebut lets leave that part out23:04
v1k0d3nthen i want to downgrade the entire openstack deployment.23:04
sdakedowngrade is a terrible example23:04
v1k0d3ncloud-native would assume that this can be done23:04
sdakebecause downgrade doesn't work with databases23:04
sdakeof any type23:04
sdakeany time you have changing state, downgrade becomes a non-starter23:05
v1k0d3ni think the end goal is that operator makes this possible eventually.23:05
sdakecan you pick a different example that i'll actually buy ;)23:05
sdakev1k0d3n - for downgrade to work, database migrations would have to be unwound23:05
sdakethis is not possible in a SQL environment23:05
sdakeand not really possible in a pure KV environment either23:05
v1k0d3nok23:05
v1k0d3nrabbit23:06
v1k0d3ni'm just saying.23:06
sdakeya rabbit is full of trouble, but it has nothign to do with dynamic scheduling23:06
sdakeand everything to do with erlang23:06
*** jtriley has quit IRC23:08
v1k0d3ni'm just worried that kolla-kubernetes could be held back because of the need for kolla-ansible.23:08
sdakecould you expand on that23:08
v1k0d3nsome of the ansible items are addressed with other, simpler options and because of the basic nature of a kubernetes deployment.23:09
v1k0d3nwhy ansible?23:09
sdakeno the held back part23:09
v1k0d3nwhy not use entry point because it breaks an ansible deployment23:09
v1k0d3n?23:09
sdakeyou mean a comma to be in that sentence?23:09
sdakewhy not use entry pooint; because it breaks an ansible deployment?23:10
*** saneax-_-|AFK is now known as saneax23:10
v1k0d3ni'd rather talk in person. just have too much going on (making dinner, errands, etc).23:11
sdakei understand but would like to hear your take before we get to kubecon23:11
v1k0d3nit's always going to come to this discussion, i guess.23:11
v1k0d3nwe're looking for a controller. i think SAP is looking for that too.23:12
v1k0d3nothers too.23:12
sdakeright a controller23:12
v1k0d3njust want to remove parity.23:12
sdakewould you consider entrypoint a controller?23:12
v1k0d3nit's a start; more than what kolla has today for kubernetes.23:12
sdakei understand it provides some functionality23:13
sdake(keep in mind i'm coing up to speed)23:13
sdakemy take on controllers is they are sort of "top down"23:13
v1k0d3ni know...it's all good.23:13
sdakemeaning they operate with dependencies in order23:13
*** saneax is now known as saneax-_-|AFK23:13
v1k0d3nthe operator (etcd/prometheus) is a controller for sure.23:14
v1k0d3nthat's the reason.23:14
sdakeok,, and entrypoint is what?23:14
sdakebesides a start - does it have a clasification23:14
v1k0d3ni said earlier, precursor to this etcd operator concept.23:15
v1k0d3nlesson's learned.23:15
sdakeso why not just write an openstack operator?23:15
v1k0d3nbut i think that it will end up being a controller eventually for that project. i would love to see that work in kolla, rather than somewhere else.23:15
sdakethat would be compatible with an ansible deployment.23:15
v1k0d3nthat's my suggestion :)23:15
v1k0d3nthat's been my whole point of this convo. hahaha23:15
sdakei thought the whole point you were making is we should use entrypoint ;)23:16
v1k0d3nwhy does it need to compatible with ansible...just a hypothetical question?23:16
v1k0d3nuntil earlier this week...yes. because it's a start.23:16
sdakesure - because we maintain one set of containers for all orchestration systems23:16
sdakenot two sets23:16
sdakeone for ansible one for kubernetes iss nutty23:16
v1k0d3n^^ agreed.23:17
v1k0d3nbut kolla cannot be deployed with salt23:17
v1k0d3nor puppet23:17
v1k0d3ntoday23:17
v1k0d3nbut if entrypoint was used...23:17
sdakewho cares23:17
v1k0d3nit could be.23:17
v1k0d3nEVERYONE CARES23:17
sdakeabout salt and puppet?23:17
v1k0d3nthat's the single run i think23:17
v1k0d3nyes.23:17
v1k0d3nit's containers...why pick an orchestrator? that becomes opinionated then.23:18
sdakewe haven't picked an orchestrator23:18
sdakewe have chosen a json API to the containers however23:18
sdakeso rather then entrypoint, why not make our own version23:18
v1k0d3nis there an architecture diagram for the json API?23:19
sdakeif we depend on a third party dep for our core runtime of containers it will come to haunt us23:19
v1k0d3nmaybe that would help?23:19
sdakev1k0d3n i dont have one23:19
sdakei can point you at the json api exmaple if you like23:19
sdakethe reason the json api was invented was so that multiple orchestration engines could be used23:20
sdakeentrypoint took angus's work there and expanded it23:20
sdakebut it was never rolled back upstream23:21
sdakeinstead it was forked off into a new thing23:21
*** neilus has joined #openstack-kolla23:21
sdakewithout our  original requirements being met23:21
sdakefwiw when angus and i had this conversation with a bunch of other people in the channel he said that his approach was wrong23:24
sdakethat was the second failure I was speaking of earlier23:24
sdakenot that I dont mind trying again23:24
sdakeif we are going to make an openstack operator, I think that makes perfect sense - lets make it work with everything we care about today (ansible, kubernetes) using the json API we have today23:25
*** HyperJohnGraham has quit IRC23:27
sdakev1k0d3n have you seen this tweet: https://twitter.com/robynbergeron/status/79210435489978777623:27
sdakev1k0d3n i could see a future outcome where each type of application (that is complex) is controlled by an operator23:34
sdakei dont think that is the same thing as entrypoint23:34
sdakeentrypoint half of the equation there23:34
v1k0d3nit's not23:37
v1k0d3nat summit...entrypoint was handing dependancies via container, not an orchestrator.23:37
v1k0d3nkubernetes does not need an orchestrator.23:37
v1k0d3nkolla-ansible does23:38
v1k0d3nso ansible holds it back23:38
v1k0d3noperator is new, better.23:38
v1k0d3nbut does ansible need it?23:38
sdakeyou mean OPENSTACK needs an orchestrator23:38
v1k0d3nyes23:38
v1k0d3nbut we are talking about kolla23:38
sdakekolla-ansible just delivers on the requirements23:38
v1k0d3nbecause kolla takes on building openstack23:39
sdakein the future it doess23:39
v1k0d3nif kolla was just containers, it would solve this via container23:39
*** neilus has quit IRC23:39
sdakeif you are talking of the repo23:39
sdakeok, well thats not going to ever happen23:39
sdakedo you know kolla's mission?23:39
v1k0d3ni belive containerized openstack23:40
v1k0d3n?23:40
sdakehttps://twitter.com/robynbergeron/status/79210435489978777623:41
sdakewrong pste23:41
sdakemoment23:41
sdakehttps://github.com/openstack/governance/blob/master/reference/projects.yaml#L2458-L245923:41
v1k0d3nlol first one is funny considering though :)23:41
sdakeya it was already in my paste buffer when i mentioned it above a screen ago ;)23:42
sdakeso our mission isn't really "containerized openstack"23:42
v1k0d3nyeah, so i understand23:42
sdakepeople could interpret that to mean "to put openstack in containers."23:42
sdakeour mission is to do that AND operate openstack with them23:42
v1k0d3ni consider it to be an openstack deployment that is prod-ready, just using containers.23:42
v1k0d3ni get it.23:43
v1k0d3nbut what kubernetes needs is different23:43
sdakeok - the reason i mention all this23:43
sdakeis because there was alot of contention early on23:43
*** neilus has joined #openstack-kolla23:43
sdakeand it persists to this day23:43
v1k0d3na container get's whacked and comes up somewhere else...is something going to orchestrate or operate that?23:43
sdakewhich is why we are making the kolla repo23:43
sdakewithin ansible?23:43
v1k0d3nso container native means that the container would be able to address that type of issue.23:43
v1k0d3nno...23:43
v1k0d3nnevermind.23:44
sdakeits all good23:44
sdakedont get frustrated ;)23:44
v1k0d3nprobably better convo for later. i really think we're on the same page.23:44
v1k0d3nbut the detail is ansible, and keeping that.23:44
v1k0d3ni get it.23:44
sdakei just want to understand what you want to propose before it gets done23:44
v1k0d3nit NEEDS to be there.23:44
v1k0d3nfor kolla-ansible23:44
v1k0d3nbut if the containers are used differently (kubernetes), than a different approach should at least be explored.23:45
sdaketotally agree23:45
v1k0d3nif it's not...people will HAVE to look at only parts of kolla.23:45
sdakewe spent all week on irc brainstorming approaches23:45
sdakethat is what kolla-kubernetes repository is about23:45
v1k0d3nso operator is a good path.23:45
v1k0d3nmy favorite.23:45
v1k0d3nit's way better than entrypoint.23:45
sdakei think your missing all this brainstorming context23:45
sdakewhat is better then entrypoint?23:46
v1k0d3nbut at the time a couple of weeks ago...entrypoint allows to not be dependent on ansible....again.23:46
v1k0d3noperator. i mentioned above.23:46
v1k0d3nwas operator mentioned last week?23:46
sdakenot at all23:46
v1k0d3ni wish i was in it...meant to be, this week has been rough23:46
sdakehere are the two independent areas of research we have underway23:47
v1k0d3nso optional operator containers for galera/mariadb, rabbit, etc...that would be great.23:47
sdakeust to bring you up to speed23:47
sdakewe have a couple dudes looking at adding dependencies to helm so helm can handle all of openstack operational experience23:47
v1k0d3nwhat is missing?23:48
sdakewe also have couple dudes looking at integrating entrypoint into our kolla_start23:48
*** neilus has quit IRC23:48
v1k0d3ni sent some things to ryan...helm can handle dependancies.23:48
sdakethe reason we have these dudes looking at this stuff is to determine which path to take23:48
sdakeit sounds like your proposing a third path, an operator23:48
v1k0d3nbut for blips, where container is rescheduled or something unexpected...operator handles this.23:48
sdakeyes it handles them incorrectly for the kolla case however23:48
v1k0d3nwe had a meeting with deis this week.23:48
v1k0d3nand also been attending the community meetings. i invited ryan to come because SAP was demoing.23:49
sdakeok, well it would be better if we could keep all the communicatio nin one place ;)23:49
sdakeso are you proposing then a third line of investigation?23:50
v1k0d3nyes. operators.23:50
v1k0d3nbecause through discussions...it keeps coming back to this.23:50
sdakeok - I think your caught up on context23:50
sdakeor possibly I'm caught up23:50
v1k0d3nhard to tell anymore :) things are moving so fast.23:51
sdakesee if we have the convo in one place, then everyone is caught up all the time ;)23:51
v1k0d3nwhat time do you get in tomorrow?23:51
sdake5pm23:51
v1k0d3nyeah, just hard to do that...because there are so many other projects involved now.23:51
sdakegoing to try to moe my flight up tho because i can23:51
v1k0d3nhelm has it;s own meetings. kubernetes has an operators meeting, or SIG-apps. there is openstack-SIG...there's just so much.23:51
sdakethese cats don't use irc?23:51
v1k0d3nnope....sorry. they use slack23:52
v1k0d3nit's where all the hipsters are now man :)23:52
sdakeya23:52
sdakeso here is the basic deal23:53
sdakean operator sounds fine23:53
sdakei'd like to investigate all 3 approaches as a community23:54
sdakeso we can find the best approach to proceed with23:54
sdakehowever, for kolla-kubernetes to work properly, it has to integrate with kolla containers23:54
*** srwilkers has quit IRC23:54
sdakefor kolla-ansible to work properly, it has to integrate with kolla-containers23:54
sdakejust because kubernetes is hip doesn't obliviate the fact that 16% of deployments are interested in kolla-ansible (today)23:55
*** srwilkers has joined #openstack-kolla23:55
sdakethat will continue to grow23:55
sdakekolla-ansible is proven and based upon well tested tech23:55
sdakeso if we make an operator, it needs to integrate with what we got23:56
sdakeor we failed our mission23:56
sdakeand let down the 500 people who have contributed to kolla over the last 26 months23:57
v1k0d3nso today, if ansible deploys out of order (serialized), will the containers be initialize correctly?23:57
v1k0d3nwhat if ansible just throws them in any order?23:57
sdakei totally get the problem you after23:57
sdakewe tried it with compose23:57
v1k0d3nso they're not the same. as it stands today, kolla containers cannot really work for kubernetes.23:57
sdakewe had something similar to entrypoint, but much more crude23:57
v1k0d3nthat's the problem.23:57
v1k0d3nkolla-ansible needs ansible.23:58
v1k0d3ncontainers need structure.23:58
v1k0d3nwhen deployed.23:58
v1k0d3ni know you understand what i'm saying.23:58
v1k0d3ni'm just trying to drive to something better.23:58
v1k0d3nand i think it can be done.23:58
sdakeit would be rockin if we could just launch all the containers and they owuld do their thing23:59
sdakewe have tried it twice23:59
sdakeboth times failed23:59
v1k0d3nyeah, that's what is needed.23:59
sdakefor different reasons23:59
v1k0d3noperator would fix that23:59
v1k0d3neven entrypoint would fix that, if the entrypoint container is called.23:59
v1k0d3nand that's why i say them together sometimes.23:59

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