Friday, 2019-01-11

*** lbragstad has quit IRC00:10
*** jamesmcarthur has joined #openstack-tc00:38
*** jamesmcarthur has quit IRC00:43
*** tosky has quit IRC01:05
*** jamesmcarthur has joined #openstack-tc01:12
*** ricolin has quit IRC01:28
fungiwhat we mostly seem to lack is people with time and interest to be project managers, but also sufficient insight into the projects involved to understand the scope of work and challenges involved01:48
*** jamesmcarthur has quit IRC01:56
*** jamesmcarthur has joined #openstack-tc01:59
*** ricolin has joined #openstack-tc02:03
*** jamesmcarthur has quit IRC02:04
*** jamesmcarthur has joined #openstack-tc02:05
*** jamesmcarthur has quit IRC02:17
*** jamesmcarthur has joined #openstack-tc02:19
*** jamesmcarthur has quit IRC02:23
*** jamesmcarthur has joined #openstack-tc02:31
*** jamesmcarthur has quit IRC02:48
*** lbragstad has joined #openstack-tc02:52
*** whoami-rajat has joined #openstack-tc03:03
*** dangtrinhnt has quit IRC03:23
*** dangtrinhnt has joined #openstack-tc03:24
*** lbragstad has quit IRC04:35
*** jamesmcarthur has joined #openstack-tc04:48
*** jamesmcarthur has quit IRC04:53
*** e0ne has joined #openstack-tc06:24
*** e0ne has quit IRC06:36
*** e0ne has joined #openstack-tc06:45
*** Luzi has joined #openstack-tc07:14
*** e0ne has quit IRC07:27
*** e0ne has joined #openstack-tc07:36
*** e0ne has quit IRC07:36
*** e0ne has joined #openstack-tc08:01
*** diablo_rojo has quit IRC08:08
*** e0ne has quit IRC08:10
*** eumel8 has joined #openstack-tc08:10
*** e0ne has joined #openstack-tc08:20
*** e0ne has quit IRC08:21
*** tosky has joined #openstack-tc08:40
*** jamesmcarthur has joined #openstack-tc08:50
*** jamesmcarthur has quit IRC08:54
*** jpich has joined #openstack-tc08:57
*** openstackgerrit has joined #openstack-tc09:46
openstackgerritAndriy Shevchenko proposed openstack/constellations master: Updatae home-page  https://review.openstack.org/63010109:46
*** e0ne has joined #openstack-tc10:01
ttxtc-members: we'll have a new "community newsletter" out next week. If you have specific bits/threads/pointers that you'd like to highlight as "openstack project news" please add to https://etherpad.openstack.org/p/newsletter-openstack-news10:14
eumel8ttx: maybe it's worth to mention the upcoming Ops Meetup in Berlin as a forecast for March: https://etherpad.openstack.org/p/ops-meetups-team10:51
*** dims has quit IRC11:21
*** dtantsur|afk is now known as dtantsur11:26
*** cmurphy is now known as cmorpheus12:05
ttxeumel8: good idea! Maybe it will appear more in an events section but should make sure to mention it yes12:20
*** cdent has joined #openstack-tc12:28
*** dtantsur is now known as dtantsur|brb12:59
*** dims has joined #openstack-tc13:01
*** dims has quit IRC13:07
*** dims has joined #openstack-tc13:07
*** jamesmcarthur has joined #openstack-tc13:28
*** jamesmcarthur has quit IRC13:28
*** jamesmcarthur has joined #openstack-tc13:56
*** lbragstad has joined #openstack-tc13:57
*** jamesmcarthur has quit IRC14:01
mnaserttx: i'd like to highlight the merge of these nova-specs: https://review.openstack.org/#/c/554218/8 and https://review.openstack.org/#/c/554212/1214:10
mnaserthat will allow for super interesting scheduling ideas.  first of all it'll allow for things like pre-empitable instances14:10
mnaserand also it allows for some crazy ideas like... shutting down hypervisors in low load periods and starting them up when demand goes up14:10
mnaseri dunno, it's a really really really cool highlight which brings ability to do cool new features and green/power saving stuff too :)14:11
cdentmnaser: i'm missing how those two enable the shut down hypervisor case, couldn't you already do that?14:12
mnasercdent: if i have 40 hvs and im using 10% of my cloud, i can shut off 90% but if demand suddenly bursts, instance schedules will always fail14:12
cdentoh, I see what you mean14:12
mnaserbut instead with this, if demand bursts, instances will sit in PENDING for a long period of time while some $background_service powers them back on, calls nova for a rebuild once capacity is there, and the vm is up14:13
mnaseravoiding a customer to do retries etc :)14:13
cdentyes, that will be nice14:14
fungisome $background_service could be ironic, i guess?14:15
fungii suppose that's the tripleo approach? if you need more hypervisors, nova schedule them onto additional undercloud bare metal instances?14:16
fungidoes indeed seem like it opens up some useful avenues14:17
smcginnisThat could be a really cool elastic capacity, project integration story if it would work that way.14:19
* fungi imagines rooms full of computers powering up and down as vm and container load demands fluctuate14:21
cdentthere are several other ways to achieve similar results14:21
fungican nova schedule virtual machines onto bare metal instances it's also managing via its ironic hypervisor driver?14:22
cdentfor example you could also watch the results of various queries to placement and spin up new hypervisors shortly before you run out, instead of introducing the latency of the pending state14:22
fungiif so, i guess that eliminates a need for tripleo's undercloud approach in that particular case14:22
cdentfungi: depends on the hypervisor invovled with the vms, but if its qemu/kvm-based, something needs to put nova-compute on the bare metal14:23
cdentbut "something" could be automaed14:24
fungior could just be baked into the image14:24
mnasercdent: thhe thing is it's pretty impossible to predict workloads14:24
mnaserlike you can get a gigantic burst that takes you from 20% to 100% capacity in minutes14:25
fungiyeah, you can try to spin up and maintain some % available cushion, but demand can easily overrun that faster than you can stay ahead of it14:26
cdentright, my thinking was that multiple approaches be available depending on the kind of patterns that particular cloud sees.14:26
mnaseryeah, and the nice thing this solves is that it eliminates a client having to 'retry'14:26
cdentyou want to be able to both be ahead of the curve, but also adapt when it gets ahead of you14:27
mnaserbut also preemptible instances story is sweet14:27
fungipreemptible instances is something aws/ec2 has had for a while, right? idea being that your instances can get paused/shelved if a higher-paying workload suddenly needs the capacity you're consuming?14:28
TheJuliamnaser: I suspect shutting down would be awesome, might just be best for some of the power sync logic to be revisited between nova/ironic in the "undercloud" case. I know cern has had some issues because nova and ironic both think they are authoritative for power control... but there are some legitimate reasons to independently power a machine on as well... like "oh, its not up, let me quickly add more ram to that box."14:30
mnaserfungi: yes, also gcp has it14:30
mnaserTheJulia: well as of right now, the "thing" that powers things on or off can be arbitrary, the idea is that nova can halt scheduling and let the user do $things before it tries again14:31
mnaserso my idea in this case is power on new computes, or maybe delete existing ephemeral vms to make space14:32
TheJuliaI think it would be cool if something automatically new to power on, or even provision new compute nodes. Tied with an inventory of hardware from ironic, it could get interesting. The one issue I see is some of the network aspects might not be ideal for a auto-scaling compute fleet14:34
TheJuliabut then again, they would just be a peaking plant14:34
mugsieis that not what watcher was supposed to be doing?14:35
* mugsie has vague memoeries of intel people talking about it in Barcelona14:35
fungii suppose this is also a good opportunity to plug the autoscaling sig which is being formed14:35
*** whoami-rajat has quit IRC14:36
fungior at least has been suggested/discussed and looks like they're about to formally propose14:36
fungiper ricolin's message to the discuss ml just now http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001656.html14:37
fungimugsie: and yeah, that thread mentioned watcher14:37
smcginnisAnyone have thoughts on the latest bot spammed patches change the home-page from www.openstack.org to the git repos? Doesn't seem correct to me.14:40
smcginnisNot even taking into consideration that cgit is going away.14:40
*** edmondsw has quit IRC14:40
fungii haven't seen those14:41
fungiaha, they even misspelled "update"14:41
fungihttps://review.openstack.org/63010114:41
smcginnishttps://review.openstack.org/#/q/owner:%22Andriy+Shevchenko%22+status:open14:41
smcginnisYeah, I had to chuckle at that.14:41
smcginnisIt your going to automate something like that, at least take two seconds to make sure you don't have a typo.14:42
fungilooks like at least some are changing them to the docs site14:42
smcginnisThat's a little better at least.14:42
ricolinfungi, :)14:43
*** jamesmcarthur has joined #openstack-tc14:48
ttxmnaser: those are nice, but is it likely to make it to Stein ? That sounds a bit abstract as an information for the general public if it's more than one release away...14:48
mnaserttx: the code for enable rebuild instances is already pushed up a while back from cern -- https://review.openstack.org/#/q/topic:bp/enable-rebuild-for-instances-in-cell0+(status:open+OR+status:merged) -- the pending stuff also is getting worked on https://review.openstack.org/#/q/topic:bp/introduce-pending-vm-state+(status:open+OR+status:merged)14:49
mnaserthat's really the "foundation" though, the next step would be leveraging those features, that might be a bit later14:49
ttxOK, been adding it to the etherpad under 'also happened', feel free to redact better14:54
cdentttx, etherpad link?14:55
*** whoami-rajat has joined #openstack-tc14:55
ttxhttps://etherpad.openstack.org/p/newsletter-openstack-news as mentioned in the ping above14:55
cdenti seem to have missed that ping14:56
* cdent looks at the logs14:56
ttxit was a tc-m*mbers one14:56
* cdent nods14:57
cdentI wasn't connected when that happened14:57
ttxeumel8: was there some kind of formal announcement for ops meetup that we could link to ? /cc: smcginnis14:57
ttxthe meeting logs are not crystal clear on the dates14:58
smcginnisttx: It's been narrowed down to that week, but I don't think we've decided the specific dates yet.14:58
ttxOK, so I think we should wait for next newsletter to announce14:59
smcginnisLet me check to make sure on that. As far as I know, we have the venue reserved, we have committed to Berlin, but we are still working out some of the specific details.14:59
ttxyeah, it's like 99% sure but would prefer 100% before making it newsletter material14:59
smcginnisAgreed, might be better to give it a week and have more details to share.15:00
smcginnisttx: I'll try to remember to ping you as soon as I hear any further decisions on that.15:01
ttxsmcginnis: I added it for reference on the etherpad (in a "future" section)15:01
smcginnis++15:02
ttxsmcginnis: any news from Adjutant regarding Stein membershipFreeze? Would like to mention it in my Stein-2 milestone snippet15:02
smcginnisttx: No, I still need to contact Adrian.15:05
*** dtantsur|brb is now known as dtantsur15:06
ttxok, we still have a few days15:08
*** edmondsw has joined #openstack-tc15:08
smcginnisToo many distractions this week. Email sent.15:11
*** jamesmcarthur has quit IRC15:13
cdentI remember that the reason I got into computers when I was wee was because the engagement was so single-minded, focused, and distraction free. I'd do some one thing on my computer for 15 hours and it was grand. Oh how things have changed.15:17
smcginnisI do remember a very short period in my career where that was normal. I miss those days.15:23
*** jamesmcarthur has joined #openstack-tc15:23
*** Luzi has quit IRC15:30
*** jamesmcarthur has quit IRC15:41
fungii remember being attracted to computers because it was a way to avoid interacting with other people ;)15:54
cdentyup15:55
smcginnisWell, there was that too. :)15:55
*** jamesmcarthur has joined #openstack-tc15:55
fungiand now, computers seem to be the primary way people interact with each other15:55
fungimy how the tables have turned15:55
*** e0ne has quit IRC16:00
*** jamesmcarthur_ has joined #openstack-tc16:05
*** e0ne has joined #openstack-tc16:08
*** jamesmcarthur has quit IRC16:09
*** evrardjp has quit IRC16:10
*** evrardjp has joined #openstack-tc16:11
*** e0ne has quit IRC16:24
*** e0ne has joined #openstack-tc16:24
*** EmilienM is now known as EvilienM16:26
openstackgerritWitold Bedyk proposed openstack/governance master: Update email address  https://review.openstack.org/63031416:30
*** e0ne has quit IRC16:39
*** jpich has quit IRC17:08
*** jpich has joined #openstack-tc17:08
openstackgerritAndriy Shevchenko proposed openstack/governance master: Update home-page  https://review.openstack.org/63034317:10
*** jpich has quit IRC17:11
openstackgerritMerged openstack/governance master: Update email address  https://review.openstack.org/63031417:22
*** jpich has joined #openstack-tc17:23
openstackgerritAndriy Shevchenko proposed openstack/governance master: Update home-page  https://review.openstack.org/63034317:27
*** jpich has quit IRC17:28
*** ricolin has quit IRC17:31
*** lbragstad has quit IRC17:35
*** tosky has quit IRC17:40
*** dtantsur is now known as dtantsur|afk17:48
*** lbragstad has joined #openstack-tc17:52
*** lbragstad has quit IRC17:56
*** lbragstad has joined #openstack-tc18:01
*** lbragstad has quit IRC18:03
*** lbragstad has joined #openstack-tc18:03
*** lbragstad_ has joined #openstack-tc18:04
*** lbragstad has quit IRC18:04
*** lbragstad_ has quit IRC18:04
*** lbragstad has joined #openstack-tc18:05
*** lbragstad_ has joined #openstack-tc18:05
*** lbragstad_ has quit IRC18:05
*** lbragstad has quit IRC18:06
*** lbragstad has joined #openstack-tc18:06
*** TheJulia is now known as needssleep18:10
*** jamesmcarthur_ has quit IRC18:18
*** lbragstad has quit IRC18:22
*** remi_ness has joined #openstack-tc18:25
*** gouthamr has quit IRC18:51
*** diablo_rojo has joined #openstack-tc18:54
*** lbragstad has joined #openstack-tc18:58
*** lbragstad has quit IRC19:39
*** lbragstad has joined #openstack-tc19:39
*** lbragstad has quit IRC19:40
*** lbragstad has joined #openstack-tc19:41
*** openstackstatus has quit IRC19:43
*** openstackstatus has joined #openstack-tc19:44
*** ChanServ sets mode: +v openstackstatus19:44
*** kmalloc has joined #openstack-tc19:50
*** kmalloc has quit IRC19:51
*** gouthamr has joined #openstack-tc19:53
*** openstack has joined #openstack-tc20:16
*** ChanServ sets mode: +o openstack20:16
*** whoami-rajat has quit IRC20:26
*** e0ne has joined #openstack-tc20:26
*** jamesmcarthur has joined #openstack-tc20:28
*** jamesmcarthur has quit IRC20:36
*** jamesmcarthur has joined #openstack-tc20:37
*** remi_ness has quit IRC20:43
*** jamesmcarthur has quit IRC20:46
*** jamesmcarthur has joined #openstack-tc20:47
*** corvus is now known as thecount21:02
*** thecount is now known as corvus21:02
*** jamesmcarthur has quit IRC21:04
*** jamesmcarthur has joined #openstack-tc21:08
*** cdent has quit IRC21:17
*** jamesmcarthur has quit IRC21:28
*** jamesmcarthur has joined #openstack-tc21:30
*** tosky has joined #openstack-tc21:42
*** jamesmcarthur has quit IRC21:43
*** jamesmcarthur has joined #openstack-tc21:55
*** jamesmcarthur has quit IRC21:57
*** EvilienM is now known as EmilienM22:14
*** gagehugo has quit IRC22:15
*** gagehugo has joined #openstack-tc22:17
*** e0ne has quit IRC22:19
*** e0ne has joined #openstack-tc22:45
*** e0ne has quit IRC22:51

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