Thursday, 2019-05-09

*** jamesmcarthur has joined #openstack-publiccloud00:04
*** jamesmcarthur has quit IRC00:05
*** jamesmcarthur has joined #openstack-publiccloud00:05
*** jamesmcarthur has quit IRC01:12
*** jamesmcarthur has joined #openstack-publiccloud01:43
*** jamesmcarthur has quit IRC01:44
*** jamesmcarthur_ has joined #openstack-publiccloud01:44
*** partlycloudy has left #openstack-publiccloud02:10
*** jamesmcarthur_ has quit IRC02:33
*** jamesmcarthur has joined #openstack-publiccloud02:34
*** ricolin has joined #openstack-publiccloud02:42
*** jamesmcarthur has quit IRC03:08
*** jamesmcarthur has joined #openstack-publiccloud03:11
*** jamesmcarthur has quit IRC03:34
*** jamesmcarthur has joined #openstack-publiccloud04:05
*** hberaud has joined #openstack-publiccloud07:39
*** hberaud is now known as hberaud|lunch09:53
*** hberaud|lunch is now known as hberaud|afk10:52
*** hberaud|afk is now known as hberaud10:52
tobberydbergReminder that we have bi-weekly meeting in 2 hours - 1400 UTC in this channel!12:01
*** gtema has joined #openstack-publiccloud12:15
*** jamesmcarthur has quit IRC12:21
*** jamesmcarthur has joined #openstack-publiccloud12:21
*** jamesmcarthur has quit IRC12:30
*** gtema has quit IRC12:37
*** gtema has joined #openstack-publiccloud12:48
*** jamesmcarthur has joined #openstack-publiccloud12:49
miougeHi there :)13:00
gtemahey13:00
*** jamesmcarthur has quit IRC13:05
*** mriedem has joined #openstack-publiccloud13:32
*** gtema has quit IRC13:40
*** NilsMagnus has joined #openstack-publiccloud13:42
*** altlogbot_0 has quit IRC13:43
*** altlogbot_2 has joined #openstack-publiccloud13:45
tobberydbergHi miouge and gtema13:47
NilsMagnusgtema is probably semi-offline, but I shall stand in13:51
NilsMagnushow was your flight back, did you re-adapt so far?13:51
NilsMagnusdo we have a minutes pad?13:53
tobberydberghttps://etherpad.openstack.org/p/publiccloud-wg13:53
tobberydbergHehehe....well...pretty horrible way back, delayed flight out of Denver, causing missed flight back to Sweden in Chicago ... staying the night there, back the next day with an extra flight, no luggage, waiting in luggage area for 4 h for first out of 2 bags .... :-)13:55
tobberydbergNot really in the timezone yet :-) How about you?13:55
miougeOuch, that doesn't sounds fun13:56
NilsMagnusI was lucky to grab an upgrade to Business, which was very slick13:56
tobberydberghehe ... that sounds a little bit better! :-)13:56
NilsMagnusBut it's a 19-hour-ride anyway13:57
tobberydbergYea, not the most fun parts of the trip :-)13:58
tobberydberg#startmeeting publiccloud_wg14:01
openstackMeeting started Thu May  9 14:01:30 2019 UTC and is due to finish in 60 minutes.  The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: publiccloud_wg)"14:01
openstackThe meeting name has been set to 'publiccloud_wg'14:01
tobberydbergHello folks! Nice to see you all here! o/14:01
tobberydbergAgenda found at https://etherpad.openstack.org/p/publiccloud-wg14:02
tobberydberg#topic 1. Migrating to SIG14:03
*** openstack changes topic to "1. Migrating to SIG (Meeting topic: publiccloud_wg)"14:03
tobberydbergMost of you were probably around in Denver, we have been talking for some time of migrating to a SIG, which will now happen ... that work is in progress14:04
tobberydbergWill not really be any different for us, just more follow where the community is going14:04
NilsMagnuschange 655354 was merged, is there anything else to do?14:05
tobberydbergThere are a few more things to be done14:06
tobberydbergrenaming stuff mostly in various places14:06
tobberydbergbut not much more than that14:06
mriedemo/14:06
tobberydbergwelcome mriedem14:06
tobberydbergQuestions on that topic?14:06
tobberydberg#topic 2. Denver discussions14:09
*** openstack changes topic to "2. Denver discussions (Meeting topic: publiccloud_wg)"14:09
tobberydbergWe had a few forum sessions14:09
tobberydberg deletion of resources and change of ownership14:10
tobberydbergGood attention on those with some good outcome14:10
*** ncastele has joined #openstack-publiccloud14:10
tobberydberg"deletion of resources" will happen, or at least a start to get the baseline in place to be able to continue that work14:10
tobberydbergMonty will implement a base in shade together with adriant14:11
mriedems/shade/openstacksdk/14:11
tobberydbergright14:12
tobberydbergalso a volunteer for the base support in OSC14:12
tobberydberggtema14:13
tobberydberg(thought he was around here earlier)14:13
ncasteledo we plan to base the work from what has been done with ospurge (https://github.com/openstack/ospurge) or starting "from scratch"?14:13
tobberydberg"Change of ownership" action from the Forum was to float that by the projects in PTG14:14
tobberydbergmelwitt did that, with the answer " I discussed the idea with the cinder and neutron teams at the PTG and they are OK with the plan"14:15
NilsMagnusgtema is probably working on the integration in SDK, not sure about OSC14:15
tobberydbergncastele - https://etherpad.openstack.org/p/DEN-Deletion-of-resources14:15
tobberydbergIt will be more "natively" integrated in the official tools/libraries (shade/openstacksdk/OSC)14:16
ncastelemake sense, thanks14:17
NilsMagnusso actually the work is done in SDK/OSC, what are actions here in PC-WG/SIG?14:17
tobberydbergInitially to followup that work14:17
NilsMagnusack14:18
tobberydbergAnd will probably also be to push that idea to the other teams once the base parts are in place14:18
tobberydbergAs you can read in the etherpad, one idea is to let every project implement a purge api call ... if that exists, use that etc etc14:19
tobberydbergBut very glad this is finally happening14:19
tobberydbergChange of ownership will be a followup task for us as well14:20
tobberydbergquestions on that before we move to the billing initiative?14:20
NilsMagnusfine with me14:21
ncastelefine with me14:21
tobberydbergso, "joint development effort for billing"14:22
tobberydbergA "thing" that has been talked a bit about over the last years basically14:22
NilsMagnusare there any written guidelines or designs for that?14:22
tobberydbergNilsMagnus not at this point no14:22
ncasteledon't think so. We all have our custom implementation14:23
tobberydbergBackground story is - all public clouds (also private clouds) do their billing today in different ways, some use official openstack projects, some don't14:23
NilsMagnusI really like the idea, but I have to admit that it might be hard to pitch this to our guys that do actual billing right now, taking into account the pain it caused in the past. That may or may not apply also to others?14:24
tobberydbergAlso, basically no one feel that the solutions offered in openstack official projects today solves their needs14:24
ncastelewe discussed in Denver about collecting our needs first, to ensure projects like Cloudkitty does not cover them14:25
tobberydbergNilsMagnus Might be so - and this is pretty early in the process as well14:25
ncasteleIt will help to limit the project also14:25
tobberydbergexactly ncastele14:25
NilsMagnusI haven't seen a pad for that. Does it make sense to open one to collect demands?14:26
tobberydbergI know a lot of us have ideas around this topic, some that are not around today as well14:26
tobberydbergYes14:26
tobberydbergMy suggestion is as follow:14:26
tobberydberg1. We create an etherpad for initial brainstorming14:27
tobberydberg2. We schedule a meeting specifically for this topic to discuss all ideas14:27
tobberydberg3. We create a spec for how this could work14:27
tobberydberg4. We reach out on mailing list to the community for feedback and thought around this14:28
tobberydbergWhat do you all think is a good way moving forward on this?14:28
NilsMagnus+1*4. Is there a naming convention on the pad's names?14:29
ncasteleI already talked with cloudkitty in Denver about our initiative, they are aware about it and understand why we are doing this, but we need to ensure they have a place somewhere in the process to avoid some "political issues" and other stuff14:29
tobberydbergNot really NilsMagnus - but maybe something like "publiccloud-sig-billing-implementation-proposal"  or something in that way :-)14:29
tobberydbergTotally agree with that ncastele14:30
miougeI'm not super familiar with Cloud Kitty, but I know of a couple of openstack public cloud using CloudKitty for rating, then sending that to their billing system14:30
tobberydbergYes. We don't use it14:31
ncastelethis is why we need to challenge cloudkitty just after the spec, and before any development, perhaps they will be able to help for some topic14:31
tobberydberg+114:31
tobberydbergDefinitely before development takes place14:32
miougeFor those using it, I do not know how much custom patches were required to get things working14:32
ncasteleI don't know any public cloud provider using cloudkitty at huge scale like some of us have, but we need to ensure why we're not using it regarding our specs14:32
tobberydbergIn this discussion we had around this we also talked about getting public clouds to put in upstream effort in this "project"14:33
tobberydbergAlso something that would be good to bring some clarity in the process, what resources we will have and what time commitment we can give into this14:34
tobberydbergToday all companies spend a lot of time implementing their own solutions, so much more worth joining up and putting some of that effort into this14:35
ncasteleyes. I know some of us are able to provide internal resources to make it work so we will probably be able to build a team around this14:36
tobberydbergI think and hope so to14:36
tobberydbergbut that will be part of the process14:37
NilsMagnusI made a new pad: https://etherpad.openstack.org/p/publiccloud-sig-billing-implementation-proposal14:37
tobberydbergMore thoughts around this at this point?14:37
tobberydberg+1 - thanks NilsMagnus14:38
tobberydbergI added it to the etherpad14:38
tobberydbergTime plan for the initial steps?14:38
miougeShould we reach out to other public clouds (like passport) to see if they are interested in participating in the billing thing?14:39
tobberydbergYes, definitely14:39
NilsMagnuswhat about collecting ideas (step 11) until next meeting?14:39
NilsMagnuss/11/114:39
tobberydbergSo maybe, an email to openstack-discuss about this first step as well?14:40
tobberydbergAgree NilsMagnus ... my thought as well!14:40
NilsMagnuswhen is next meeting? now()+2 weeks?14:41
tobberydbergyes14:41
NilsMagnusso, May 2314:41
tobberydbergThat is right (and shit, on customer visit in Germany that day) :-) But will try to solve that some how :-)14:42
tobberydbergI can reach out to the mailing list and public clouds that doesn't read that list that much as well and try to get them in here as well14:43
tobberydbergMore on this topic at this point?14:43
tobberydbergEveryone ok with above plan?14:43
ncasteleno more here, discussion will start when we will share our needs :)14:44
tobberydberg:-)14:44
tobberydbergif not more in this, over to next and last agenda topic...14:45
tobberydberg#topic 3. Other topics14:45
*** openstack changes topic to "3. Other topics (Meeting topic: publiccloud_wg)"14:45
tobberydbergAny other topics that anyone would like to raise?14:46
ncastelenope14:47
*** gtema has joined #openstack-publiccloud14:47
NilsMagnusThe change-of-ownership is just an implementation detail on the deletion subject?14:47
tobberydbergno, separate "thing"14:47
tobberydberghttps://etherpad.openstack.org/p/DEN-change-ownership-of-resources14:48
NilsMagnusjust asking' as it is on the agenda14:48
tobberydbergjust touched it briefly above14:48
tobberydbergwe will do followup on that, but as of today, that discussion took place in the cross project team meetings at the PTG14:49
NilsMagnusok14:49
tobberydbergIt was nice talking to you all in Denver! Also nice that you turned up here today! :-)14:50
gtemaI am also here, sadly a bit late14:51
tobberydbergwelcome gtema :-)14:51
NilsMagnusIs there some folklore here to conclude a meeting? Everyone singing a song? The chairman doing some special dance?14:52
gtemathanks. Since I am also participating in the project_cleanup dev - you are free to ping/ask me14:52
tobberydberggreat gtema - we will do followup in that moving forward, and also, feel free to bring status updates here if or/and when you have that =)14:53
ncasteleAgree to sing a song, only if it's a Katy Perry's one14:53
gtemaoki14:53
gtemano Katy Perry please14:53
tobberydberghaha NilsMagnus - happy that we don't do video calls just now ;-)14:53
gtemaAnother brick in the wall of Openstack !!14:54
tobberydbergI guess we will have a forum session around ending ceremony in Shanghai ;-)14:54
NilsMagnustoo bad, it looked like for a second that gtema volunteered for Katy Perry :)14:54
gtemano way Nils14:55
ncasteleI also started to be happy, but this meeting is definitely ending bad from my point of view :(14:55
tobberydberg5 more minutes to raise a topic ... or sing a song... ;-)14:55
ncastelehopefully I can trust Spotify to give me some KP14:56
gtemawell, if people like Kate - I'm fine, it's just I will not sing it ;-)14:57
tobberydberg:-)14:57
ncasteleI think I'm the only one going for KP, and as I'm quite new (first time on IRC :o ), I'll not push too much for KP, let's stay discreet14:58
tobberydberghehe14:59
tobberydbergSo I guess time is up, and some of you will go listen to KP... ;-) Thanks for today all! Looking forward to next meeting and what ideas we can proved until then!15:00
ncasteleYes, thanks for the discussion, see u in two weeks15:00
gtemagreat. See you15:00
tobberydbergo/15:00
tobberydberg#endmeeting15:00
*** openstack changes topic to "New meeting time!! Thursday odd weeks at 1400 UTC in this channel!!"15:00
openstackMeeting ended Thu May  9 15:00:38 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/publiccloud_wg/2019/publiccloud_wg.2019-05-09-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/publiccloud_wg/2019/publiccloud_wg.2019-05-09-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/publiccloud_wg/2019/publiccloud_wg.2019-05-09-14.01.log.html15:00
NilsMagnuscya15:02
*** jamesmcarthur has joined #openstack-publiccloud15:13
*** mriedem has left #openstack-publiccloud15:19
*** trident has quit IRC15:33
*** trident has joined #openstack-publiccloud15:35
*** hberaud is now known as hberaud|school-r15:41
*** hberaud|school-r is now known as hberaud15:49
*** hberaud is now known as hberaud|afk15:50
*** hberaud|afk is now known as hberaud15:54
*** jamesmcarthur has quit IRC16:34
*** ricolin has quit IRC16:45
*** irclogbot_2 has quit IRC16:46
*** irclogbot_3 has joined #openstack-publiccloud16:47
*** ncastele has quit IRC17:00
*** gtema has quit IRC17:14
*** jamesmcarthur has joined #openstack-publiccloud18:34
*** jamesmcarthur has quit IRC18:38
*** NilsMagnus has quit IRC18:45
*** jamesmcarthur has joined #openstack-publiccloud18:47
*** jamesmcarthur has quit IRC19:17
*** jamesmcarthur has joined #openstack-publiccloud19:31
*** jamesmcarthur has quit IRC19:39
*** jamesmcarthur has joined #openstack-publiccloud19:50
*** jamesmcarthur has quit IRC20:23
*** hberaud is now known as hberaud|gone20:53
*** damien_r has joined #openstack-publiccloud20:53
*** damien_r has quit IRC20:53
*** damien_r has joined #openstack-publiccloud20:53
*** jamesmcarthur has joined #openstack-publiccloud20:54
*** logan- has quit IRC21:00
*** logan- has joined #openstack-publiccloud21:03
*** jamesmcarthur has quit IRC21:05
*** jamesmcarthur has joined #openstack-publiccloud21:17
*** jamesmcarthur has quit IRC21:21
*** dasp has quit IRC21:52
*** damien_r has quit IRC22:06
*** trident has quit IRC22:19
*** trident has joined #openstack-publiccloud22:22
adrianttobberydberg: I've added some notes about existing solution regarding billing to that etherpad22:38
adriantCatalyst built our own, which is opensource, and we support. It isn't exactly any better than cloudkitty, but not exactly worse either.22:39
adriantWe built it a long time ago (2013-14?) and have refactored and changed it a few times since, with more planned work on it as we go, with me adding support to it for cron like asyc billing module for exporting data for invoices. Which for us would be a daily triggered process that looks for any accounts which need to billed (has the month finished,22:44
adriantand usage collection is up to date for that account), or account terminations (so we can send out their final invoice right away). It would then create and send the invoices via our ERP system.22:44
adriantWe tried merging it cloudkitty, or working with them to fill some of our gaps and move to cloud kitty, but found that process to not be what we wanted to go down.22:54
adriantTo be fair I'm likely to do massive rewrites of Distil (and maybe a v3) down the line as I do some work... So I'd potentially be willing to work on a community set of requirements for what other clouds need as a billing solution.23:13
adriantI have to support Distil v2 as is, but would be willing to even collaborate on a greenfields project for a new and better community drive design (if it also fulfils our needs).23:14
*** jamesmcarthur has joined #openstack-publiccloud23:36

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