| *** wojdev has joined #openstack-meeting-4 | 00:06 | |
| *** banix has joined #openstack-meeting-4 | 00:13 | |
| *** david-lyle is now known as david-lyle_afk | 00:14 | |
| *** wojdev has quit IRC | 00:17 | |
| *** ajmiller has quit IRC | 00:49 | |
| *** banix has quit IRC | 00:51 | |
| *** banix has joined #openstack-meeting-4 | 00:52 | |
| *** banix has quit IRC | 00:52 | |
| *** SumitNaiksatam has quit IRC | 00:58 | |
| *** salv-orlando has quit IRC | 01:00 | |
| *** fnaval has quit IRC | 01:04 | |
| *** xgerman has quit IRC | 01:09 | |
| *** banix has joined #openstack-meeting-4 | 01:10 | |
| *** VW_ has quit IRC | 01:11 | |
| *** SridharRamaswam1 has joined #openstack-meeting-4 | 01:14 | |
| *** SridharRamaswamy has quit IRC | 01:15 | |
| *** banix has quit IRC | 01:18 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 01:44 | |
| *** dannywilson has joined #openstack-meeting-4 | 02:03 | |
| *** dannywilson has quit IRC | 02:13 | |
| *** dannywilson has joined #openstack-meeting-4 | 02:13 | |
| *** dannywilson has quit IRC | 02:18 | |
| *** banix has joined #openstack-meeting-4 | 02:45 | |
| *** markvoelker has quit IRC | 02:47 | |
| *** markvoelker has joined #openstack-meeting-4 | 02:47 | |
| *** carl_baldwin has joined #openstack-meeting-4 | 02:48 | |
| *** markvoelker has quit IRC | 02:51 | |
| *** yamahata has quit IRC | 02:52 | |
| *** rm_work has quit IRC | 03:10 | |
| *** Aish has quit IRC | 03:11 | |
| *** carl_baldwin has quit IRC | 03:13 | |
| *** carl_baldwin has joined #openstack-meeting-4 | 03:15 | |
| *** sbalukoff has quit IRC | 03:34 | |
| *** markvoelker has joined #openstack-meeting-4 | 03:43 | |
| *** Aish has joined #openstack-meeting-4 | 03:44 | |
| *** carl_baldwin has quit IRC | 03:51 | |
| *** carl_baldwin has joined #openstack-meeting-4 | 03:58 | |
| *** carl_baldwin has quit IRC | 04:14 | |
| *** ajmiller has joined #openstack-meeting-4 | 04:21 | |
| *** SridharRamaswam1 has quit IRC | 04:32 | |
| *** rm_work|away has joined #openstack-meeting-4 | 04:36 | |
| *** rm_work|away is now known as rm_work | 04:36 | |
| *** rm_work has joined #openstack-meeting-4 | 04:36 | |
| *** markvoelker has quit IRC | 04:44 | |
| *** markvoelker has joined #openstack-meeting-4 | 04:45 | |
| *** markvoelker has quit IRC | 04:49 | |
| *** banix has quit IRC | 04:51 | |
| *** ivar-laz_ has joined #openstack-meeting-4 | 04:56 | |
| *** ivar-lazzaro has quit IRC | 04:59 | |
| *** yamahata has joined #openstack-meeting-4 | 05:00 | |
| *** asselin_ has quit IRC | 05:11 | |
| *** carl_baldwin has joined #openstack-meeting-4 | 05:19 | |
| *** hareeshp has joined #openstack-meeting-4 | 05:20 | |
| *** jckasper has joined #openstack-meeting-4 | 05:23 | |
| *** hareeshpc has joined #openstack-meeting-4 | 05:28 | |
| *** hareeshp has quit IRC | 05:31 | |
| *** fnaval has joined #openstack-meeting-4 | 05:32 | |
| *** carl_baldwin has quit IRC | 05:42 | |
| *** sarob has quit IRC | 06:01 | |
| *** sarob has joined #openstack-meeting-4 | 06:03 | |
| *** sarob has quit IRC | 06:08 | |
| *** smillward has quit IRC | 06:12 | |
| *** smillward has joined #openstack-meeting-4 | 06:12 | |
| *** sbalukoff has joined #openstack-meeting-4 | 06:18 | |
| *** sarob has joined #openstack-meeting-4 | 06:30 | |
| *** sarob has quit IRC | 06:41 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 06:43 | |
| *** numan has joined #openstack-meeting-4 | 06:56 | |
| *** hareeshpc has quit IRC | 07:02 | |
| *** belmoreira has joined #openstack-meeting-4 | 07:03 | |
| *** ibiris is now known as ibiris_away | 07:11 | |
| *** sarob has joined #openstack-meeting-4 | 07:13 | |
| *** pkoniszewski has joined #openstack-meeting-4 | 07:13 | |
| *** sarob has quit IRC | 07:18 | |
| *** ibiris_away is now known as ibiris | 07:19 | |
| *** wojdev has joined #openstack-meeting-4 | 07:20 | |
| *** wojdev has quit IRC | 07:20 | |
| *** markvoelker has joined #openstack-meeting-4 | 07:44 | |
| *** kobis has joined #openstack-meeting-4 | 07:44 | |
| *** Aish has quit IRC | 07:44 | |
| *** markvoelker has quit IRC | 07:50 | |
| *** matrohon has joined #openstack-meeting-4 | 08:14 | |
| *** salv-orlando has joined #openstack-meeting-4 | 08:39 | |
| *** wojdev has joined #openstack-meeting-4 | 08:42 | |
| *** hareeshp has joined #openstack-meeting-4 | 08:47 | |
| *** kobis1 has joined #openstack-meeting-4 | 08:51 | |
| *** kobis has quit IRC | 08:52 | |
| *** yamahata has quit IRC | 08:53 | |
| *** hareeshp has quit IRC | 09:02 | |
| *** ibiris is now known as ibiris_away | 09:11 | |
| *** evgenyf has joined #openstack-meeting-4 | 09:13 | |
| *** sarob has joined #openstack-meeting-4 | 09:14 | |
| *** Aish has joined #openstack-meeting-4 | 09:17 | |
| *** Aish has left #openstack-meeting-4 | 09:17 | |
| *** sarob has quit IRC | 09:19 | |
| *** ibiris_away is now known as ibiris | 09:22 | |
| *** jemangs_ has quit IRC | 09:32 | |
| *** jemangs has joined #openstack-meeting-4 | 09:34 | |
| *** hareeshp has joined #openstack-meeting-4 | 09:43 | |
| *** markvoelker has joined #openstack-meeting-4 | 09:47 | |
| *** numan has quit IRC | 09:49 | |
| *** salv-orlando has quit IRC | 09:49 | |
| *** evgenyf has quit IRC | 09:50 | |
| *** markvoelker has quit IRC | 09:52 | |
| *** evgenyf has joined #openstack-meeting-4 | 09:58 | |
| *** numan has joined #openstack-meeting-4 | 10:01 | |
| *** [1]evgenyf has joined #openstack-meeting-4 | 10:02 | |
| *** wojdev has quit IRC | 10:05 | |
| *** evgenyf has quit IRC | 10:05 | |
| *** [1]evgenyf is now known as evgenyf | 10:05 | |
| *** wojdev has joined #openstack-meeting-4 | 10:06 | |
| *** VW_ has joined #openstack-meeting-4 | 10:07 | |
| *** sarob has joined #openstack-meeting-4 | 10:16 | |
| *** sarob has quit IRC | 10:21 | |
| *** hareeshp has quit IRC | 10:26 | |
| *** hareeshp has joined #openstack-meeting-4 | 10:28 | |
| *** kobis1 has quit IRC | 10:31 | |
| *** kobis has joined #openstack-meeting-4 | 10:32 | |
| *** VW_ has quit IRC | 11:03 | |
| *** hareeshp has quit IRC | 11:04 | |
| *** asselin_ has joined #openstack-meeting-4 | 11:06 | |
| *** asselin_ has quit IRC | 11:11 | |
| *** wojdev has quit IRC | 11:11 | |
| *** salv-orlando has joined #openstack-meeting-4 | 11:15 | |
| *** hareeshp has joined #openstack-meeting-4 | 11:16 | |
| *** sarob has joined #openstack-meeting-4 | 11:17 | |
| *** hareeshp has quit IRC | 11:21 | |
| *** sarob has quit IRC | 11:22 | |
| *** VW_ has joined #openstack-meeting-4 | 11:30 | |
| *** bobmel has joined #openstack-meeting-4 | 11:32 | |
| *** bobmel_ has quit IRC | 11:35 | |
| *** VW__ has joined #openstack-meeting-4 | 11:38 | |
| *** VW__ has quit IRC | 11:39 | |
| *** VW__ has joined #openstack-meeting-4 | 11:39 | |
| *** VW_ has quit IRC | 11:41 | |
| *** salv-orlando has quit IRC | 11:44 | |
| *** hareeshp has joined #openstack-meeting-4 | 12:17 | |
| *** wojdev has joined #openstack-meeting-4 | 12:23 | |
| *** rfolco has joined #openstack-meeting-4 | 12:35 | |
| *** bobmel has quit IRC | 12:39 | |
| *** bobmel has joined #openstack-meeting-4 | 12:40 | |
| *** bobmel has quit IRC | 12:44 | |
| *** markvoelker has joined #openstack-meeting-4 | 12:50 | |
| *** salv-orlando has joined #openstack-meeting-4 | 12:54 | |
| *** markvoelker has quit IRC | 12:56 | |
| *** rfolco has quit IRC | 12:56 | |
| *** jckasper has quit IRC | 13:06 | |
| *** wojdev has quit IRC | 13:10 | |
| *** galstrom_zzz is now known as galstrom | 13:14 | |
| *** wojdev has joined #openstack-meeting-4 | 13:21 | |
| *** banix has joined #openstack-meeting-4 | 13:26 | |
| *** bobmel has joined #openstack-meeting-4 | 13:27 | |
| *** ajmiller has quit IRC | 13:28 | |
| *** bobmel has quit IRC | 13:31 | |
| *** hemanthm is now known as __hemanthm | 13:35 | |
| *** hemanthm has joined #openstack-meeting-4 | 13:37 | |
| *** wojdev has quit IRC | 13:38 | |
| *** krykowski has joined #openstack-meeting-4 | 13:45 | |
| *** bobmel has joined #openstack-meeting-4 | 13:50 | |
| *** markvoelker has joined #openstack-meeting-4 | 13:53 | |
| *** stevelle has joined #openstack-meeting-4 | 13:55 | |
| *** klamath has joined #openstack-meeting-4 | 13:56 | |
| *** wayne__ has joined #openstack-meeting-4 | 13:56 | |
| *** klamath has quit IRC | 13:56 | |
| *** klamath has joined #openstack-meeting-4 | 13:57 | |
| *** wojdev has joined #openstack-meeting-4 | 13:57 | |
| *** Olena has joined #openstack-meeting-4 | 13:58 | |
| *** markvoelker has quit IRC | 13:59 | |
| *** ativelkov has joined #openstack-meeting-4 | 13:59 | |
| *** sigmavirus24_awa is now known as sigmavirus24 | 13:59 | |
| nikhil_k | #startmeeting Glance | 14:00 |
|---|---|---|
| openstack | Meeting started Thu Feb 26 14:00:15 2015 UTC and is due to finish in 60 minutes. The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| *** openstack changes topic to " (Meeting topic: Glance)" | 14:00 | |
| openstack | The meeting name has been set to 'glance' | 14:00 |
| hemanthm | o/ | 14:00 |
| ativelkov | o/ | 14:00 |
| kragniz | o/ | 14:00 |
| nikhil_k | https://etherpad.openstack.org/p/glance-team-meeting-agenda | 14:00 |
| *** ivasilevskaya has joined #openstack-meeting-4 | 14:00 | |
| stevelle | o/ | 14:00 |
| mfedosin | o/ | 14:00 |
| *** lakshmiS has joined #openstack-meeting-4 | 14:00 | |
| krykowski | o/ | 14:01 |
| ivasilevskaya | o/ | 14:01 |
| nikhil_k | #info K-3 FF proposal date is Mar 12 for Glance | 14:01 |
| *** rosmaita has joined #openstack-meeting-4 | 14:02 | |
| sigmavirus24 | o/ | 14:02 |
| nikhil_k | That means, all the feature related code needs to be proposed & merged by that date | 14:02 |
| Olena | o/ | 14:02 |
| rosmaita | o/ | 14:02 |
| lakshmiS | o/ | 14:02 |
| nikhil_k | https://launchpad.net/glance/+milestone/kilo-3 | 14:02 |
| nikhil_k | Please take a look at that and try to review the linked features + Artifacts on priority | 14:03 |
| *** asselin_ has joined #openstack-meeting-4 | 14:03 | |
| nikhil_k | mfedosin: ativelkov : Can anyone of you add Artifacts related BPs to k3? | 14:03 |
| *** rfolco has joined #openstack-meeting-4 | 14:04 | |
| ativelkov | nikhil_k: sure. Do you want a single artifacts BP or separate BPs for each commit? | 14:04 |
| mfedosin | nikhil_k, sure, we're working on it | 14:04 |
| nikhil_k | ativelkov: as many specs we've, | 14:04 |
| pkoniszewski | o/ | 14:04 |
| nikhil_k | please update their milestone to be k3 | 14:04 |
| ativelkov | this means two: one for semver and another one for eveything else | 14:05 |
| nikhil_k | yes | 14:05 |
| ativelkov | ok | 14:05 |
| nikhil_k | (unless discussions from here on call for any other one, I'm trying to be generic) | 14:05 |
| nikhil_k | Also, we've had several requests about https://blueprints.launchpad.net/glance/+spec/sighup-conf-reload | 14:06 |
| nikhil_k | I just wanted for someone with enough cycles to test that functionally and double check if we did not miss anything | 14:06 |
| nikhil_k | #topic Question: grouping artifacts by type version in the list output (as proposed on mini-summit) | 14:07 |
| *** openstack changes topic to "Question: grouping artifacts by type version in the list output (as proposed on mini-summit) (Meeting topic: Glance)" | 14:07 | |
| nikhil_k | Who proposed that? | 14:08 |
| sigmavirus24 | ativelkov: ? | 14:08 |
| nikhil_k | ativelkov: looks like you? | 14:08 |
| sigmavirus24 | (going by color) | 14:08 |
| ativelkov | yes | 14:08 |
| ativelkov | Just a quick question | 14:08 |
| ativelkov | on the mini-summit there was a proposal to group artifacts by the version of their type | 14:08 |
| ativelkov | I mean, in the "list artifacts" API output | 14:09 |
| ativelkov | in case if the type version is not specified | 14:09 |
| ativelkov | This remains an action item on me, so I wanted to clarify if that is a good idea or not | 14:10 |
| *** markvoelker has joined #openstack-meeting-4 | 14:10 | |
| nikhil_k | I stand +1 on that | 14:10 |
| hemanthm | I'm wondering if we necessarily have to do it by default | 14:10 |
| ativelkov | Why can't it be done on client side? | 14:11 |
| hemanthm | how about we provide a param for grouping | 14:11 |
| ativelkov | The problem with it is sorting and getting the marker for pagination iteration | 14:11 |
| ativelkov | if this is just a plain list, then the id of the last record is the marker for the next page request | 14:12 |
| ativelkov | if the output is grouped then there is no such thing as a "last record" | 14:12 |
| nikhil_k | ativelkov: true, that makes things a bit complex | 14:13 |
| *** mclaren has joined #openstack-meeting-4 | 14:13 | |
| ativelkov | and the sorting order between items in different group cannot be easily defined if the client wants to compare them | 14:13 |
| nikhil_k | ativelkov: ok, how bad would it be to do on glaceclient? | 14:14 |
| ativelkov | on the contrary, grouping may be always done on the client-side, as the records contain all the needed fields | 14:14 |
| ativelkov | nikhil_k: that's what I wanted to suggest: leave it for client(s) | 14:14 |
| sigmavirus24 | And sorted() is rather fast once we have all the records | 14:14 |
| nikhil_k | ativelkov: ah ok, so supported client and not the consumers. cool | 14:14 |
| *** galstrom is now known as galstrom_zzz | 14:15 | |
| nikhil_k | sigmavirus24: the worry there is that, people might want to fetch more records out of the DB frquently | 14:15 |
| *** salv-orlando has quit IRC | 14:15 | |
| sigmavirus24 | nikhil_k: yep | 14:15 |
| ativelkov | So, if everybody agrees, then I drop that action item: we'll leave API call to output just list of items, not groups | 14:16 |
| nikhil_k | sure, please keep a note on the spec that mentions this drawback | 14:17 |
| hemanthm | ativelkov, was there a good usecase for grouping by default? | 14:17 |
| ativelkov | hemanthm: I don't know - this was said by somebody at the summit | 14:17 |
| ativelkov | I didn't remember the usecase behind that. | 14:18 |
| nikhil_k | hemanthm: The general feeling was about usability. Not having to go through all the non relavant artifacts | 14:18 |
| *** TravT_ has joined #openstack-meeting-4 | 14:18 | |
| nikhil_k | ok, we can discuss the details offline if that's ok | 14:19 |
| ativelkov | nikhil_k: if you want to get only the relevant ones, you may always specify type version explicitly | 14:19 |
| *** hareeshpc has joined #openstack-meeting-4 | 14:19 | |
| kragniz | nikhil_k: isn't that where filtering would be more useful? | 14:19 |
| ativelkov | e.g. GET /v2/artifacts/someType/v1.2/ | 14:19 |
| *** asselin_ has quit IRC | 14:19 | |
| nikhil_k | #info ativelkov to update the Artifacts spec to state that grouping of API results is too complicated due to pagination | 14:19 |
| *** sarob has joined #openstack-meeting-4 | 14:20 | |
| nikhil_k | kragniz: ativelkov : true but if you've multiple ones and are doing something between browsing and searching then this becomes relevant | 14:20 |
| nikhil_k | can we move on? | 14:21 |
| nikhil_k | I think we can discuss the details offline and/or on ML | 14:22 |
| ativelkov | sure | 14:22 |
| *** hareeshp has quit IRC | 14:22 | |
| nikhil_k | #topic Abandoning stale PS from review | 14:22 |
| *** openstack changes topic to "Abandoning stale PS from review (Meeting topic: Glance)" | 14:22 | |
| nikhil_k | https://etherpad.openstack.org/p/glance-cleanout-of-inactive-PS | 14:22 |
| nikhil_k | http://comments.gmane.org/gmane.comp.cloud.openstack.devel/46352 | 14:23 |
| nikhil_k | Please reply to that thread if you've something to say | 14:23 |
| *** TravT_ is now known as TravT | 14:24 | |
| nikhil_k | Guess jokke_ proposed that and is not around so, may be we'd move on | 14:24 |
| kragniz | yeah, move on | 14:24 |
| *** pennerc has joined #openstack-meeting-4 | 14:24 | |
| nikhil_k | #topic python-glanceclient release 0.16.0 | 14:24 |
| *** openstack changes topic to "python-glanceclient release 0.16.0 (Meeting topic: Glance)" | 14:24 | |
| nikhil_k | http://osdir.com/ml/openstack-dev/2015-02/msg01858.html | 14:25 |
| nikhil_k | http://docs.openstack.org/developer/python-glanceclient/#id1 | 14:25 |
| *** sarob has quit IRC | 14:25 | |
| nikhil_k | (I think it was jokke_ again who proposed that topic ??) | 14:25 |
| sigmavirus24 | or pkoniszewski | 14:26 |
| nikhil_k | That's all the relevant info, (I think) we need | 14:26 |
| sigmavirus24 | or krykowski | 14:26 |
| sigmavirus24 | heh | 14:26 |
| nikhil_k | #topic Questionable reviews | 14:26 |
| *** openstack changes topic to "Questionable reviews (Meeting topic: Glance)" | 14:26 | |
| sigmavirus24 | Ohai that's me | 14:26 |
| nikhil_k | https://review.openstack.org/#/c/159068/ | 14:26 |
| nikhil_k | sigmavirus24: sure | 14:27 |
| sigmavirus24 | So https://review.openstack.org/#/c/159068/ is questionable because it presents a serious backwards compatibility issue with the glanceclient | 14:27 |
| pennerc | o/ | 14:27 |
| sigmavirus24 | It's also indicative of the fact that we either need to dedicate more time to bug triaging so people don't just pick up non-triaged bugs | 14:27 |
| sigmavirus24 | The less tangential question here is: Do we even want to require a name for a created image? | 14:28 |
| rosmaita | it's weird not to have one, but as long as there's a uuid, who cares? | 14:28 |
| sigmavirus24 | Commenting on that review/bug would be helpful | 14:28 |
| sigmavirus24 | rosmaita: right and if the API doesn't require one, why should the client is the bigger question | 14:28 |
| nikhil_k | I'd just -2 it as that was the original use case, name is not a required attr so we'd not force it | 14:29 |
| rosmaita | sigmavirus24: you are correct, the "official" glanceclient should respect the API, private glance clients can do whatever they like | 14:29 |
| sigmavirus24 | The bug was never discussed either | 14:29 |
| sigmavirus24 | rosmaita: right | 14:29 |
| sigmavirus24 | ativelkov: kragniz other thoughts? | 14:30 |
| nikhil_k | sigmavirus24: I do not think that discussions are mandatory on bugs before someone picks it up. Many times the bugs are filed because you're working on something | 14:30 |
| kragniz | I agree with rosmaita | 14:30 |
| *** VW__ has quit IRC | 14:30 | |
| ativelkov | Well, I agree that if the name is not required, then we should not enforce it in glance cli. | 14:30 |
| mclaren | seems a bit late for a v1 change of this kind IMHO | 14:30 |
| nikhil_k | heh | 14:31 |
| *** VW_ has joined #openstack-meeting-4 | 14:31 | |
| *** hareeshp has joined #openstack-meeting-4 | 14:31 | |
| rosmaita | looking at the api docs, name is not marked as optional ... but there is no uniqueness requirement, and an empty string is a string, so ... | 14:32 |
| ativelkov | I think that this discussion (allowing to create images without a name) happens periodically :) | 14:32 |
| sigmavirus24 | So the other one, I added before Flavio and nikhil_k chimed in but everyone should still take a look at the bug: https://launchpad.net/bugs/1279832 and review: https://review.openstack.org/#/c/158982/ | 14:32 |
| openstack | Launchpad bug 1279832 in python-glanceclient "nova image-list can run slowly." [Wishlist,In progress] - Assigned to Shashwat Srivastava (shashwat-srivastava) | 14:32 |
| *** flaper87 has joined #openstack-meeting-4 | 14:33 | |
| flaper87 | o/ | 14:33 |
| flaper87 | why does this keep happening to me? | 14:34 |
| sigmavirus24 | Anyway, I think we can move on unless people want to discuss those further | 14:34 |
| flaper87 | sigmavirus24: thanks for the ping | 14:34 |
| sigmavirus24 | flaper87: you're welcome | 14:34 |
| *** hareeshpc has quit IRC | 14:34 | |
| sigmavirus24 | I'll ping you more often and regularly in the future =P | 14:34 |
| flaper87 | sigmavirus24: THANK YOU! | 14:34 |
| flaper87 | :D | 14:34 |
| nikhil_k | hmm, flaper87 good point. may be I need a courtesy ping | 14:34 |
| flaper87 | nikhil_k: please please please | 14:34 |
| flaper87 | I'd really appreciate it | 14:34 |
| flaper87 | I do have a calendar reminder | 14:34 |
| flaper87 | I just don't have a calendar | 14:35 |
| sigmavirus24 | we need a meeting bot that pings people in #openstack-glance | 14:35 |
| flaper87 | :P | 14:35 |
| nikhil_k | cool | 14:35 |
| sigmavirus24 | Just don't create an action item for that =P | 14:35 |
| nikhil_k | #topic glance_store release 0.1.11 status | 14:35 |
| *** openstack changes topic to "glance_store release 0.1.11 status (Meeting topic: Glance)" | 14:35 | |
| nikhil_k | http://lists.openstack.org/pipermail/openstack-dev/2015-February/057386.html | 14:35 |
| nikhil_k | https://launchpad.net/glance-store/v0/v0.1.11 | 14:35 |
| nikhil_k | List glance_store 0.1.11 in https://trello.com/b/GFXMXxsP/openstack-glance | 14:35 |
| * flaper87 clicks and clicks | 14:36 | |
| * flaper87 loves those dogs | 14:36 | |
| nikhil_k | thanks to flaper87 , that trello board is readable in public (public read access is tested, if you cannot hit it please refresh or try a different tab/browser) | 14:36 |
| nikhil_k | that's on on that from me | 14:36 |
| nikhil_k | moving on.. | 14:36 |
| *** wojdev has quit IRC | 14:37 | |
| flaper87 | :) | 14:37 |
| nikhil_k | #topic glance_store release 0.1.12 | 14:37 |
| *** openstack changes topic to "glance_store release 0.1.12 (Meeting topic: Glance)" | 14:37 | |
| nikhil_k | https://launchpad.net/glance-store/+milestone/v0.1.12 | 14:37 |
| nikhil_k | https://trello.com/b/GFXMXxsP/openstack-glance | 14:37 |
| nikhil_k | We usually set a tentative date on the release so that people are aware | 14:38 |
| mclaren | kragniz: we should add our socket leak fixes to the 0.16.1 client release? | 14:38 |
| flaper87 | I need to sync again with cindy to understand the status of the glance_store refactor | 14:38 |
| flaper87 | but It'd be lovely to have it in 0.1.12 | 14:38 |
| nikhil_k | If you need some specific ones in a particular release, the dates can be adjusted +2 days | 14:38 |
| flaper87 | Do we want a glance_store release before the Kilo release ? | 14:38 |
| kragniz | mclaren: I was looking at 0.17.0 for those | 14:38 |
| flaper87 | like 2 weeks after K-3 ? | 14:38 |
| nikhil_k | Another reason why the release can be delayed: there aren't enough commits to be released | 14:38 |
| * flaper87 literally made that up | 14:39 | |
| mclaren | kragniz: they unbreak nova though, so high priority in my view... | 14:39 |
| nikhil_k | One release would be a bit before K3 | 14:39 |
| nikhil_k | Mar16th or so | 14:39 |
| *** wojdev has joined #openstack-meeting-4 | 14:40 | |
| sigmavirus24 | mclaren: they're not backwards incompat and they're bug fixes so +1 on 0.16.1 if we can get them reviewed | 14:40 |
| * flaper87 confused are we talking about the client or glance_store ? | 14:40 | |
| flaper87 | :P | 14:40 |
| nikhil_k | flaper87: store | 14:40 |
| kragniz | mclaren: yeah, good point | 14:40 |
| nikhil_k | flaper87: some are talking about client | 14:40 |
| * flaper87 rolls eyes :P | 14:40 | |
| mclaren | sorry, speaking of turn... | 14:40 |
| flaper87 | re glance_store it sounds good to have 1 or even 2 minor releases before Kilo :) | 14:41 |
| flaper87 | There are still things that are a must fix before kilo goes out like the chunk/offset handling | 14:41 |
| flaper87 | zhiyan: has patches for that | 14:41 |
| nikhil_k | flaper87: sure (just trying to not break any gates and keep things smooth at the release week) | 14:41 |
| nikhil_k | if we can get those patches reviewed soon, it'd be awesome | 14:42 |
| flaper87 | I'll make that a priority for me | 14:42 |
| nikhil_k | appreciate it | 14:42 |
| nikhil_k | #topic Metadef Notifications | 14:42 |
| *** openstack changes topic to "Metadef Notifications (Meeting topic: Glance)" | 14:42 | |
| zhiyan | Thanks for you incoming review | 14:42 |
| nikhil_k | TravT: wanna go? | 14:43 |
| TravT | This review is ready, we think: https://review.openstack.org/#/c/148546/ | 14:43 |
| TravT | krykowski: updated it last night with outstanding comments | 14:43 |
| nikhil_k | nice | 14:43 |
| krykowski | yup, its in really good shape ;) | 14:43 |
| nikhil_k | krykowski: you might want to check the jenkins failure though | 14:44 |
| nikhil_k | people _may_ not review something that has -1 on it already | 14:44 |
| TravT | hmm I don't see a jenkins failure | 14:45 |
| krykowski | it has +1 from Jenkins | 14:45 |
| krykowski | Jenkins is a good guy :) | 14:45 |
| nikhil_k | TravT: krykowski : my bad, I confused you for flaper87 | 14:45 |
| kragniz | a grave mistake | 14:45 |
| nikhil_k | sorry about that, we'r good | 14:45 |
| TravT | always a good idea to assume flaper87 has jenkins failures? | 14:45 |
| TravT | ;) | 14:46 |
| nikhil_k | (and I'm asleep) | 14:46 |
| nikhil_k | anyways, moving on.. | 14:46 |
| sigmavirus24 | TravT: that was harsh =P | 14:46 |
| nikhil_k | #topic glanceclient next few releases | 14:46 |
| *** openstack changes topic to "glanceclient next few releases (Meeting topic: Glance)" | 14:46 | |
| nikhil_k | TravT: heh, just something that I was looking at and switched the tabs before coming back to IRC window :P | 14:47 |
| nikhil_k | https://launchpad.net/python-glanceclient/+milestone/v0.16.1 | 14:47 |
| *** sarob has joined #openstack-meeting-4 | 14:47 | |
| nikhil_k | #info This is due next week. | 14:47 |
| nikhil_k | https://trello.com/b/GFXMXxsP/openstack-glance | 14:48 |
| nikhil_k | card name glanceclient 0.16.1 | 14:48 |
| nikhil_k | One more is created in LP scheduled to be released a few days before K3 | 14:49 |
| nikhil_k | https://launchpad.net/python-glanceclient/+milestone/v0.17.0 | 14:49 |
| *** carl_baldwin has joined #openstack-meeting-4 | 14:49 | |
| nikhil_k | mclaren: Did you have something to mention for that earlier? | 14:49 |
| flaper87 | TravT: LOL, is that because I always do? :P | 14:49 |
| mclaren | nikhil_k: yeah | 14:49 |
| sigmavirus24 | flaper87: that was the joke ;) | 14:49 |
| TravT | flaper87: wondered if you were still listening ;-) | 14:49 |
| mclaren | nikhil_k: can I just add to that launchpad ticket? (What's the process?) | 14:50 |
| flaper87 | sigmavirus24: no no, I'm serious, I always do :P | 14:50 |
| nikhil_k | mclaren: yes, please feel free to add it to LP. We're using the trello board to see if there are any blockers | 14:50 |
| * flaper87 clicks on the client card | 14:50 | |
| nikhil_k | LP can get crowded sometimes | 14:50 |
| mclaren | https://review.openstack.org/#/c/157516/ and https://review.openstack.org/#/c/156975/ | 14:51 |
| kragniz | mclaren: do you mean target bugs to a release? | 14:51 |
| kragniz | mclaren: you can do it from the launchpad bug page | 14:51 |
| mclaren | we found that nvoa and cinder would fall over due to too many open fiel descripters | 14:51 |
| flaper87 | re client, I need to get back to this: https://review.openstack.org/#/c/140336/ | 14:51 |
| kragniz | ("target to milestone") | 14:51 |
| flaper87 | but I don't think it should block the release | 14:51 |
| flaper87 | so, feel free to move that one to the next release | 14:51 |
| flaper87 | (if needed) | 14:52 |
| *** sarob has quit IRC | 14:52 | |
| nikhil_k | flaper87: please do so, if possible for 0.16.1 | 14:53 |
| nikhil_k | moving on.. | 14:53 |
| nikhil_k | #topic Multivalue operator support | 14:53 |
| *** openstack changes topic to "Multivalue operator support (Meeting topic: Glance)" | 14:53 | |
| nikhil_k | pkoniszewski: that's you | 14:53 |
| mclaren | kragniz: looks like I added them telepathically :-) | 14:53 |
| pkoniszewski | thank you | 14:53 |
| kragniz | mclaren: that was me :P | 14:53 |
| sigmavirus24 | mclaren: mind controls kragniz ... good to know ;) | 14:54 |
| kragniz | sigmavirus24: it's a problem | 14:54 |
| * flaper87 wonders who mind controls mclaren | 14:54 | |
| pkoniszewski | so both patch sets are in a really good shape, actually both had +2 on (had to add two points to spec that zhiyan requested so it dropped) | 14:54 |
| pkoniszewski | I'd like to ask for final review there https://review.openstack.org/#/c/147264/ - specification | 14:54 |
| sigmavirus24 | pkoniszewski: 2 tiny nits from me and then I'm +2 on the spec | 14:54 |
| sigmavirus24 | (sorry) | 14:54 |
| pkoniszewski | and the code - https://review.openstack.org/#/c/148213/ | 14:54 |
| pkoniszewski | sure, leave them and i'll address it asap | 14:55 |
| *** jckasper has joined #openstack-meeting-4 | 14:55 | |
| pkoniszewski | thanks a lot! | 14:55 |
| * sigmavirus24 is going to look at the code now | 14:55 | |
| pkoniszewski | thats all for me | 14:55 |
| *** jckasper_ has joined #openstack-meeting-4 | 14:55 | |
| nikhil_k | thanks pkoniszewski, I think based on the momentum we can try to get them in this week | 14:55 |
| * sigmavirus24 is so glad to see zhiyan doing reviews again | 14:55 | |
| sigmavirus24 | == nikhil_k | 14:55 |
| nikhil_k | me too :) | 14:56 |
| nikhil_k | #topic Open Discussion | 14:56 |
| *** openstack changes topic to "Open Discussion (Meeting topic: Glance)" | 14:56 | |
| mfedosin | Folks, I am glad to introduce you our technical writer Olena :) | 14:56 |
| zhiyan | For spec ? Or code? | 14:56 |
| sigmavirus24 | zhiyan: both | 14:56 |
| flaper87 | *cough* https://review.openstack.org/#/c/159129/ *cough* | 14:56 |
| sigmavirus24 | Hi Olena ! | 14:56 |
| flaper87 | damnit, gate failure (facepalm) | 14:56 |
| Olena | hi Guys! | 14:56 |
| zhiyan | Revised spec you have a good eyes | 14:56 |
| flaper87 | Olena: HEY! :) | 14:56 |
| Olena | I am excited to join the Glance team | 14:56 |
| sigmavirus24 | flaper87: high five jenkins in the face instead ;) | 14:56 |
| flaper87 | sigmavirus24: good idea, gooooood idea! | 14:57 |
| krykowski | Olena: Hi :) | 14:57 |
| sigmavirus24 | :D | 14:57 |
| Olena | =) | 14:57 |
| nikhil_k | flaper87: http://giphy.com/gifs/cough-ToLQAiSdwq33G | 14:57 |
| rosmaita | Olena: welcome! | 14:57 |
| flaper87 | nikhil_k: huahuahauhauhau | 14:57 |
| zhiyan | Welcome! | 14:57 |
| TravT | welcome Olena! | 14:57 |
| flaper87 | good thing the other 2 are green | 14:57 |
| flaper87 | (jenkins green, not the other green) | 14:58 |
| nikhil_k | Welcome Olena ! | 14:58 |
| sigmavirus24 | I just want to point out that https://review.openstack.org/#/c/140151/ will be unnecessary for any one using requests 2.5.3 or higher but it is still absolutely necessary for anyone using anything less than that | 14:58 |
| rosmaita | Olena: maybe you can revise this page: https://wiki.openstack.org/wiki/Glance-where-are-the-docs | 14:58 |
| flaper87 | sigmavirus24: jeeeez, I wanted to get back to that one last week | 14:58 |
| flaper87 | I'll review it asap | 14:58 |
| sigmavirus24 | flaper87: thank you | 14:58 |
| nikhil_k | sigmavirus24: yes, thanks for bringing that up. | 14:58 |
| * sigmavirus24 needs to stop working upstream of openstack so he can complain about himself | 14:58 | |
| Olena | and I will take a look as well | 14:58 |
| *** wojdev has quit IRC | 14:59 | |
| *** jckasper has quit IRC | 14:59 | |
| nikhil_k | Olena: Thanks for your feedback on the docs that mfedosin shared with us a few days back! | 14:59 |
| Olena | oh, my pleasure | 14:59 |
| nikhil_k | Olena: please do let know if we can help you get familiar with Glance | 15:00 |
| nikhil_k | #openstack-glance is the place we're hiding in :) | 15:00 |
| Olena | =) okay | 15:00 |
| nikhil_k | ok, thanks all for joining.. | 15:00 |
| flaper87 | o/ | 15:00 |
| kragniz | nikhil_k: thanks! | 15:00 |
| kragniz | Olena: and hi! | 15:00 |
| nikhil_k | #endmeeting | 15:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:01 | |
| openstack | Meeting ended Thu Feb 26 15:01:00 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-26-14.00.html | 15:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-26-14.00.txt | 15:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-26-14.00.log.html | 15:01 |
| *** TravT has left #openstack-meeting-4 | 15:01 | |
| *** flaper87 has left #openstack-meeting-4 | 15:01 | |
| *** ativelkov has left #openstack-meeting-4 | 15:01 | |
| *** stevelle has left #openstack-meeting-4 | 15:01 | |
| *** wayne__ has quit IRC | 15:01 | |
| *** ivasilevskaya has left #openstack-meeting-4 | 15:01 | |
| *** pennerc has left #openstack-meeting-4 | 15:01 | |
| *** mclaren has quit IRC | 15:01 | |
| *** Olena has quit IRC | 15:01 | |
| *** rosmaita has left #openstack-meeting-4 | 15:04 | |
| *** lakshmiS has quit IRC | 15:06 | |
| *** wojdev has joined #openstack-meeting-4 | 15:09 | |
| *** yamahata has joined #openstack-meeting-4 | 15:11 | |
| *** salv-orlando has joined #openstack-meeting-4 | 15:14 | |
| *** markvoelker has quit IRC | 15:21 | |
| *** markvoelker has joined #openstack-meeting-4 | 15:21 | |
| *** matrohon has quit IRC | 15:22 | |
| *** krykowski has quit IRC | 15:22 | |
| salv-orlando | by "what we have" I mean the current algorithm | 15:22 |
| sigmavirus24 | salv-orlando: wrong channel? | 15:22 |
| salv-orlando | sigmavirus24: yeah... can I blame my dog or cat for this? | 15:23 |
| sigmavirus24 | salv-orlando: of course you can :D | 15:23 |
| *** hemanthm has left #openstack-meeting-4 | 15:24 | |
| *** hareeshpc has joined #openstack-meeting-4 | 15:25 | |
| *** markvoelker has quit IRC | 15:26 | |
| *** wojdev_ has joined #openstack-meeting-4 | 15:27 | |
| *** wojdev has quit IRC | 15:28 | |
| *** wojdev_ is now known as wojdev | 15:28 | |
| *** hareeshp has quit IRC | 15:29 | |
| *** sarob has joined #openstack-meeting-4 | 15:32 | |
| *** igordcard has joined #openstack-meeting-4 | 15:32 | |
| *** VW_ has quit IRC | 15:33 | |
| *** VW_ has joined #openstack-meeting-4 | 15:34 | |
| *** ibiris is now known as ibiris_away | 15:38 | |
| *** hareeshpc has quit IRC | 15:39 | |
| *** ajmiller has joined #openstack-meeting-4 | 15:41 | |
| *** wojdev has quit IRC | 15:44 | |
| *** sarob has quit IRC | 15:44 | |
| *** ibiris_away is now known as ibiris | 15:46 | |
| *** mattt has joined #openstack-meeting-4 | 15:48 | |
| *** igordcard has quit IRC | 15:50 | |
| *** MarkAtwood has joined #openstack-meeting-4 | 15:50 | |
| *** markvoelker has joined #openstack-meeting-4 | 15:51 | |
| *** b3rnard0 has joined #openstack-meeting-4 | 15:51 | |
| *** stevelle has joined #openstack-meeting-4 | 15:57 | |
| *** igordcard has joined #openstack-meeting-4 | 15:58 | |
| *** yamahata has quit IRC | 16:00 | |
| *** Sam-I-Am has joined #openstack-meeting-4 | 16:01 | |
| *** cloudnull has joined #openstack-meeting-4 | 16:01 | |
| *** xgerman has joined #openstack-meeting-4 | 16:02 | |
| *** git-harry has joined #openstack-meeting-4 | 16:02 | |
| b3rnard0 | #startmeeting OpenStack Ansible Meeting | 16:02 |
| openstack | Meeting started Thu Feb 26 16:02:34 2015 UTC and is due to finish in 60 minutes. The chair is b3rnard0. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:02 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:02 |
| *** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)" | 16:02 | |
| openstack | The meeting name has been set to 'openstack_ansible_meeting' | 16:02 |
| sigmavirus24 | o/ | 16:02 |
| b3rnard0 | #topic Agenda & rollcall | 16:02 |
| *** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)" | 16:02 | |
| cloudnull | present | 16:02 |
| mancdaz | hello | 16:02 |
| b3rnard0 | #link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting | 16:02 |
| d34dh0r53 | pres ent | 16:02 |
| b3rnard0 | 'ello! | 16:03 |
| stevelle | hello | 16:03 |
| mattt | o/ | 16:03 |
| Apsu | preSent | 16:03 |
| b3rnard0 | #topic Review action items from last week | 16:03 |
| *** odyssey4me has joined #openstack-meeting-4 | 16:03 | |
| *** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)" | 16:03 | |
| odyssey4me | o/ | 16:03 |
| Sam-I-Am | hi | 16:03 |
| palendae | Hi | 16:03 |
| b3rnard0 | I did not see any meeting conflicts, so I think we are good to go for this room/meeting time | 16:04 |
| *** kobis has quit IRC | 16:04 | |
| b3rnard0 | d34dh0r53 update blueprint with template from cloudnull -- status? | 16:05 |
| d34dh0r53 | done | 16:05 |
| b3rnard0 | cloudnull ping jhesketh about creating a separate repo -- status? | 16:05 |
| cloudnull | i pinged him, but have to ping him again about all the things needed. | 16:06 |
| cloudnull | that should be carried. | 16:06 |
| b3rnard0 | #action cloudnull continue pinging jhesketh about creating a separate repo and other things | 16:06 |
| b3rnard0 | BjoernT to help out with reviewing open PRs https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment,n,z -- status? | 16:07 |
| *** aventerav has joined #openstack-meeting-4 | 16:07 | |
| sigmavirus24 | Bjoern isn't here | 16:07 |
| b3rnard0 | okay, adding that as ongoing | 16:07 |
| odyssey4me | I suppose that's more of an info item anyway. | 16:07 |
| *** sigmavirus24 is now known as Slackwarebot | 16:07 | |
| *** Slackwarebot is now known as sigmavirus24 | 16:07 | |
| b3rnard0 | #info BjoernT to help out with reviewing open PRs https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment,n,z | 16:08 |
| b3rnard0 | #topic Blueprints | 16:08 |
| *** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)" | 16:08 | |
| *** BjoernT has joined #openstack-meeting-4 | 16:08 | |
| cloudnull | odyssey4me: you have the mic | 16:08 |
| b3rnard0 | #link https://blueprints.launchpad.net/openstack-ansible/+spec/apt-package-pinning | 16:08 |
| BjoernT | hey | 16:08 |
| b3rnard0 | #link https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration | 16:08 |
| odyssey4me | alright - apt pinning | 16:09 |
| b3rnard0 | hello BjoernT : we missed you :-) | 16:09 |
| *** KLevenstein has joined #openstack-meeting-4 | 16:09 | |
| BjoernT | yes my calendar alarm popped up to early to I got carried away | 16:09 |
| odyssey4me | essentially apt-pinning is one part of helping to make a consistant environment to reduce the possibility of unexpected changes in upstream apt repositories from affecting a production environment | 16:09 |
| odyssey4me | this is not the same as freezing a repository source - I'm looking into options there as a separate item which I think will go into a separate blueprint | 16:10 |
| palendae | odyssey4me: Do we know how apt behaves if you pin a version and it gets removed from the repos? | 16:11 |
| odyssey4me | the idea here is simply to be able to pin a known set of important packages at a particular version, and to ensure that the list of packages is configurable by a user of os-ansible-deployment | 16:11 |
| cloudnull | palendae it dies in a fire | 16:11 |
| odyssey4me | palendae I would think that it'll just fail an apt-get install... | 16:11 |
| Apsu | odyssey4me: I disagree it's not the same as freezing. You may not be copying packages but you still have to A) identify the set of packages to consider as a unit in order to pin them and B) continue this process as a form of continual maintenance to update over time. | 16:11 |
| odyssey4me | but if the package is already there, it should be fine | 16:11 |
| Apsu | odyssey4me: Freezing is the same thing, just copying/packaging vs pinning. | 16:11 |
| cloudnull | odyssey4me: for kilo could this be an rpc-extras thing? | 16:12 |
| *** VW_ has quit IRC | 16:12 | |
| Apsu | Both methods require package-set focused testing to try to identify what the right combination of versions is. | 16:12 |
| cloudnull | arguing that deployers may have a frozen image / repo that they want to use | 16:12 |
| odyssey4me | Apsu: I think that's largely an academic discussion. The purpose of the pinning framework is not to have an entire copy of a repo, or even a partial copy... it's rather to configure apt to respect that you want a specific set of packages kept at a certain level. | 16:12 |
| cloudnull | Im defining image as an iso / net boot image. | 16:13 |
| cloudnull | and their pinning may be different than what we've stated should be pinned, with regard to ap | 16:13 |
| cloudnull | *apt | 16:13 |
| odyssey4me | The maintenance of the pinning list we provide in the project is ours to live with, but a deployer is capable of putting their own process in to augment/override that. | 16:13 |
| odyssey4me | anyway, the blueprint's focus is to provide the capability to do pinning... | 16:14 |
| *** erikmwilson has joined #openstack-meeting-4 | 16:15 | |
| odyssey4me | we have already done so in icehouse/juno, but for master I'm looking at something a little more robust | 16:15 |
| BjoernT | We do pin already , or is this not really implemented and we put a file in place | 16:15 |
| odyssey4me | BjoernT see my last statement :) | 16:15 |
| mancdaz | BjoernT we removed the pinning in master, kind of | 16:16 |
| cloudnull | right, but if we pin enforcing pinning of packages outside of our control, IE we're not providing a repo for them to be downloaded from, I'd argue again that deployers will balk at the potential of pinning packages that do not exist. | 16:16 |
| cloudnull | just playing devils advocate here. | 16:17 |
| odyssey4me | cloudnull sure, this is why I started looking at a more holistic view | 16:17 |
| mancdaz | but the versions would be configurable? | 16:17 |
| mancdaz | so they can pin to a version they do have in their repo | 16:17 |
| *** VW_ has joined #openstack-meeting-4 | 16:17 | |
| *** VW_ has quit IRC | 16:17 | |
| odyssey4me | this was highlighted specifically when a package was pulled from Ubuntu's LTS repo | 16:17 |
| palendae | mancdaz: I think cloudnull's saying if they don't carry the package at all | 16:17 |
| cloudnull | mancdaz they would be configurable, but what if i wanted to deploy using 14.10 | 16:17 |
| BjoernT | Hmm, we from the support team wrapping up currently all the pining stuff which goes towards frozen apt repos on rackspace mirrors so pining will be another requirement so double seal it | 16:17 |
| mancdaz | well that's a whole different kettle of fish | 16:17 |
| *** VW_ has joined #openstack-meeting-4 | 16:18 | |
| Apsu | I think as soon as you have to actually do the process of picking a set of "vital" packages to pin, is the exact instant you've begun a frozen repo. For one thing, regular (fast) upstream repos don't keep long archives of previous package versions for a given distro release. Which means you need to copy the packages somewhere else and maintain that set yourself. | 16:18 |
| cloudnull | mancdaz: or debian 7 | 16:18 |
| odyssey4me | BjoernT exactly | 16:18 |
| Apsu | So even if your argument is the list is small, it's still a requirement. | 16:18 |
| git-harry | Why not say this is deployer responsibility and then if there is a community clamour for something it can be revisited. | 16:18 |
| mancdaz | cloudnull well yeah, or centos etc | 16:18 |
| odyssey4me | having a frozen repo is one part, pinning is an extra protection on top of it | 16:18 |
| BjoernT | right | 16:18 |
| cloudnull | there's nothing techincally stopping us from doing that now. we just dont support it | 16:18 |
| odyssey4me | this allows you to update your repo without causing an update across infrastructure entirely, then you can release/update the pins seperately in stages (if you want) | 16:18 |
| BjoernT | Because I know that some packages just install their own apt sources and then they might override the rackspace mirrors | 16:19 |
| mancdaz | odyssey4me or you do what we do with the python packages, in that you only provide the right version in the frozen repo | 16:19 |
| mancdaz | hence no pinnig needed | 16:19 |
| BjoernT | Yes, I agree, no pinning needed to python | 16:19 |
| BjoernT | since we don't install apt packages in the first place | 16:19 |
| odyssey4me | mancdaz yes, except as BjoernT has just mentioned, what happens if there's another repo on the host (like the default sources.list) | 16:20 |
| odyssey4me | so the way I see it it's a combination of the two to really seal it | 16:20 |
| Apsu | odyssey4me: An alternate solution is to make your repo updates use different series names, based on the revision of the software that matches the repo update, so a given deployment that's pointed at a previous series won't see the new packages anyway | 16:20 |
| BjoernT | +1 | 16:20 |
| odyssey4me | 1) provide the ability to pin | 16:20 |
| odyssey4me | 2) provide a frozen repo solution, similar to the python frozen repo solution | 16:20 |
| Apsu | That's actually what I originally proposed during the primary "to freeze or not to freeze" discussions. | 16:20 |
| odyssey4me | 1 gets used to allow staged updates in an environment | 16:21 |
| odyssey4me | 2 is the backing repository | 16:21 |
| Apsu | I.e., instead of a series target like "trusty" in your deployment repo, you have a semver tag, matching the code revision that goes along with the package set that was tested with that code revision at deployment time. | 16:21 |
| odyssey4me | I'd like to separate the two items as, generally, pinning is actually not a bad stop-gap for the short-term needs... | 16:22 |
| Apsu | Then you get pinning automagically, and can update your repo as you desire -- under new series targets. | 16:22 |
| mancdaz | Apsu yes, except for the case mentioned above where someone drops a different sources.list entry | 16:22 |
| mancdaz | pointing at trusty, or w/e | 16:22 |
| odyssey4me | To have a repo mirror and freeze it, especially within our gating infrastructure, is slightly complicated. Do-able, but it'll take longer to get to a working state. | 16:22 |
| Apsu | odyssey4me: We actually had one going already. It's just that it was determined to not be a good investment of resources to have to actually do the frozen-repo-ownership-and-testing-and-maintenance part. | 16:23 |
| odyssey4me | So, in order to try and keep the discussion clear and on-point - I ask that we keep the view that the two items, while linked, are separate. | 16:23 |
| Apsu | Because it's an awful lot of work to test and identify the versions. | 16:24 |
| *** ibiris is now known as ibiris_away | 16:24 | |
| Apsu | I'll stop derailing now. I just think actually accomplishing a pinning config is a major microcosm of freezing, and has identical challenges and resource costs. | 16:24 |
| *** andymccr has joined #openstack-meeting-4 | 16:25 | |
| BjoernT | I would skin the cat from a different way, QE tests one version with latest packages for instance. If good, generate a list of packages/version and use that to create the repos | 16:25 |
| odyssey4me | Apsu: yes, a full frozen repo is more complex... which is why I'd like to keep the topic on pinning first, we can get to z frozen repo method later | 16:25 |
| *** dannywilson has joined #openstack-meeting-4 | 16:25 | |
| odyssey4me | BjoernT that's similar to the idea I have in mind - something that is relatively low maintenance and easily generated | 16:25 |
| odyssey4me | the aim would be that a deployer of os-ansible-deployment would be able to generate a working set for their environment... but anyone who does many deploys or who wants to generate a working set for a versioned release can also do that | 16:26 |
| odyssey4me | but again, now we're talking frozen repo... the blueprint is for putting the pinning infrastructure down first | 16:27 |
| odyssey4me | so, technically, this is entirely off-topic | 16:27 |
| odyssey4me | I'm hoping to have a blueprint ready for a frozen repo discussion next week, or perhaps a week after | 16:27 |
| cloudnull | BjoernT: but again to argue both sides, why does Rackspace QE get to say what goes into that set of "good packages"? there has to be some other criteria? so any solution should be flexible enough to work outside of the Rackspace private cloud. | 16:28 |
| mancdaz | odyssey4me so aside from just adding package versions to the package names that apt installs, what is the blueprint framework achieving? | 16:28 |
| cloudnull | odyssey4me sounds good. | 16:28 |
| b3rnard0 | #info odyssey4me I'm hoping to have a blueprint ready for a frozen repo discussion next week, or perhaps a week after | 16:28 |
| odyssey4me | mancdaz there are a few things to agree on | 16:28 |
| odyssey4me | 1) using the debops.apt_preferences Ansible Galaxy role, instead of developing something specific to os-ansible-deployment | 16:29 |
| odyssey4me | is everyone happy with that approach? | 16:29 |
| cloudnull | +1 | 16:29 |
| BjoernT | cloudnull: Because they sign off on a tested package/RPC release set. They don't care what version we use in terms of apt packages | 16:29 |
| BjoernT | cloudnull: So they don't have a say, we just give them the latest versions we think are appropriate | 16:30 |
| cloudnull | right BjoernT thats an RPC thing | 16:30 |
| andymccr | is this an extras thing though or should it go in the os-ansible-deployment repo? It feels a bit like this is a "how we deploy openstack specifically" rather than a more general thing. | 16:30 |
| cloudnull | ^ thats what im arguing | 16:31 |
| Apsu | Technically it has nothing to do with os-ansible-deployment. | 16:31 |
| Apsu | It's the environment o-a-d lives in. | 16:31 |
| d34dh0r53 | +10 | 16:31 |
| odyssey4me | any opinions around using debops.apt_preferences as the role to handle pinning from now in master? or do we need to give everyone time to review and form an opinion? | 16:31 |
| cloudnull | i like the ability for a package pinning framework using the upstream role. | 16:31 |
| *** mrhillsman has joined #openstack-meeting-4 | 16:31 | |
| *** prometheanfire has joined #openstack-meeting-4 | 16:31 | |
| cloudnull | but idk if its a os-ansible-deployment thing, or an rpc thing | 16:31 |
| Apsu | Separating concerns, o-a-d isn't concerned with its environment as long as it 'works' in the way it expects. Which is primarily a question of python and minor tooling, which are already specified in the pip wheel system. | 16:32 |
| andymccr | i'd say rpc - imho | 16:32 |
| b3rnard0 | odyssey4me: we could put it out for comments/feedback and vote on it next week | 16:32 |
| Apsu | OS package pinning/freezing is moreso a question of avoiding bugs in those bits. | 16:32 |
| mancdaz | surely if you're providing anyone who uses o-a-d the opportunity to pin packages cleanly, it is an o-a-d thing? | 16:32 |
| odyssey4me | ok, so I understand the view - but I would argue that it benefits os-ansible-deployment in that it helps with our development process... specifically with gating | 16:32 |
| palendae | No arguments against debops.apt_preferences, but the o-a-d vs rpc discussions is important | 16:32 |
| git-harry | What about soliciting feedback from the mailing list as to whether os package management should be part of the project? | 16:32 |
| b3rnard0 | #info odyssey4me: 1) using the debops.apt_preferences Ansible Galaxy role, instead of developing something specific to os-ansible-deployment -- is everyone happy with that approach? | 16:32 |
| cloudnull | git-harry: that sounds like a good idea . | 16:33 |
| b3rnard0 | #info odyssey4me: any opinions around using debops.apt_preferences as the role to handle pinning from now in master? or do we need to give everyone time to review and form an opinion? | 16:33 |
| odyssey4me | if we pin stuff we use in-repo, then we avoid unnecessary distractions while we're trying to get os-ansible-deployment right | 16:33 |
| b3rnard0 | git-harry: thanks for volunteering on that! | 16:33 |
| git-harry | b3rnard0: I think you mean odyssey4me | 16:34 |
| odyssey4me | git-harry agreed, and I will send a mail out regarding the blueprint and soliciting feedback | 16:34 |
| odyssey4me | I just want to do some tweaks before I do so. | 16:34 |
| palendae | git-harry: Which mailing-list were you referring to? openstack-dev? | 16:34 |
| b3rnard0 | #action odyssey4me Solicit feedback from the mailing list as to whether os package management should be part of the project? | 16:34 |
| mattt | openstack-operators may be well suited also | 16:35 |
| git-harry | palendae: and the other one | 16:35 |
| cloudnull | i'd say both | 16:35 |
| mancdaz | all the lists | 16:35 |
| odyssey4me | I'll do both. | 16:35 |
| palendae | So we'll have both public and private discussions of it? | 16:35 |
| b3rnard0 | #info for odyssey4me action, send out to the openstack-dev and openstack-operators mailing list | 16:35 |
| Apsu | mancdaz: https://www.drupal.org/files/x-all-the-things-template.png | 16:36 |
| *** david-lyle_afk is now known as david-lyle | 16:36 | |
| cloudnull | ok, we've beaten this BP to death. lets get it on the ML once its ready and we'll go from there. | 16:36 |
| Apsu | Sorry, and you're welcome. Carry on :) | 16:36 |
| cloudnull | palendae: so long as its a bp on o-a-d its a public discussion . | 16:36 |
| palendae | cloudnull: ok, I wasn't sure what 'the other one' git-harry was referring to was | 16:37 |
| cloudnull | ah. | 16:37 |
| cloudnull | no point on putting it on our internal MLs | 16:37 |
| palendae | ^ | 16:37 |
| git-harry | palendae: sorry, yeah I meant openstack | 16:37 |
| palendae | Agreed | 16:37 |
| cloudnull | NEXT: BP | 16:37 |
| cloudnull | Implement tunables for all OpenStack roles -- odyssey4me | 16:38 |
| * cloudnull hands mic to odyssey4me | 16:38 | |
| odyssey4me | right | 16:38 |
| odyssey4me | so see the BP as an idea, not necessarily well formed at this stage | 16:39 |
| odyssey4me | we're often getting requests for 'please add the ability to configure <x> in <y>.conf' | 16:39 |
| odyssey4me | that goes through a cycle of adding some variables, and the motions of test and release | 16:40 |
| BjoernT | yes, that will only increase the more we roll RPC out | 16:40 |
| git-harry | Yeah, I don't see the point in hard coding templates | 16:40 |
| odyssey4me | slowly, over time, we're going to end up with a ton of variables and may also end up with a situation where many of them don't apply any more | 16:40 |
| odyssey4me | (as upstream has removed/changed them) | 16:40 |
| odyssey4me | so I was thinking that perhaps we can introduce the concept of tunables | 16:40 |
| palendae | odyssey4me, BjoernT: Would that relate to https://bugs.launchpad.net/openstack-ansible/+bug/1424525 then? | 16:41 |
| openstack | Launchpad bug 1424525 in openstack-ansible trunk "Make policy.json configurable / replaceable" [Medium,Triaged] - Assigned to Nolan Brubaker (palendae) | 16:41 |
| odyssey4me | simply put, have our base required stuff as the variables as we do now | 16:41 |
| andymccr | we did used to have almost exactly what you describe in the bp for a few of the openstack projects | 16:41 |
| odyssey4me | but allow other bits to be added into tunables | 16:41 |
| odyssey4me | then, for any deployment, these tunables can be set as desired | 16:41 |
| odyssey4me | very flexible, future proof | 16:41 |
| BjoernT | the policy is probably different from normal key/value template changes | 16:41 |
| palendae | Ok | 16:41 |
| cloudnull | so we did have this before and it didn't work really well. IE https://github.com/stackforge/os-ansible-deployment/blob/icehouse/rpc_deployment/vars/config_vars/keystone_config.yml https://github.com/stackforge/os-ansible-deployment/blob/icehouse/rpc_deployment/roles/keystone_common/templates/template_gen | 16:42 |
| odyssey4me | palendae that bug is a different kettle of fish | 16:42 |
| palendae | odyssey4me: Ok, carry on then :) | 16:42 |
| cloudnull | the issue was related to our support team having to manage all of that. | 16:42 |
| odyssey4me | cloudnull that, I would say, is exactly how not to do it | 16:43 |
| cloudnull | but if we're good with that, it does making it flexable. | 16:43 |
| odyssey4me | that is far worse than what I'm proposing | 16:43 |
| odyssey4me | what I'm saying is that we keep the essentials in normal variables, assigned in the normal ways | 16:43 |
| andymccr | the problem is | 16:43 |
| cloudnull | and add generators to specific things ? | 16:44 |
| git-harry | half and half is a bad idea | 16:44 |
| andymccr | if you want to override a certain var you have to override the whole nova_conf_settings: var for example? | 16:44 |
| odyssey4me | it's the fringe settings that should be tunable in the manner I'm suggesting - settings which may or may not exist yet | 16:44 |
| *** kobis has joined #openstack-meeting-4 | 16:44 | |
| cloudnull | which will result in 1 request to add a "normal" item and another on how to add something complext to the generator. | 16:44 |
| git-harry | andymccr: recursion | 16:45 |
| *** hareeshp has joined #openstack-meeting-4 | 16:45 | |
| cloudnull | but if we can think of a better way to make it work, i'm down. | 16:45 |
| cloudnull | itll fix a never ending request. | 16:45 |
| Apsu | ^ | 16:45 |
| *** fnaval has joined #openstack-meeting-4 | 16:45 | |
| odyssey4me | I think the idea needs development, and there are positive and negative aspects to each approach... | 16:46 |
| odyssey4me | but yes, I really do think that it'll help us focus development effort in the right places and can make things super flexible (and reduce turnaround) for deployers | 16:46 |
| b3rnard0 | do we want to solicit feedback as well for this blueprint? | 16:47 |
| cloudnull | agreed. its an awesome idea. | 16:47 |
| odyssey4me | so I'd like to recruit volunteers to help develop the idea | 16:47 |
| odyssey4me | perhaps what I could do is prepare an email with a variety of approaches and send it to the ML list | 16:47 |
| cloudnull | im down to help, but it may be good to get some other opinions in there. | 16:47 |
| b3rnard0 | +1 | 16:47 |
| odyssey4me | but, I'd like someone to help come up with those approaches | 16:47 |
| odyssey4me | someone(s) | 16:48 |
| odyssey4me | :) | 16:48 |
| * cloudnull looks around for volunteers | 16:48 | |
| b3rnard0 | #info odyssey4me: perhaps what I could do is prepare an email with a variety of approaches and send it to the ML list | 16:48 |
| mancdaz | I like the 'do it all in one' rather than half and half | 16:48 |
| mancdaz | I volunteer git-harry | 16:48 |
| * b3rnard0 prepares the voluntell machine | 16:48 | |
| cloudnull | hahahaha | 16:48 |
| mancdaz | git-harry has quite a good clear idea of how it could work | 16:48 |
| cloudnull | boom typie typie, make it go | 16:49 |
| cloudnull | git-harry voluntold. | 16:49 |
| git-harry | I'm allergic to being voluntold | 16:49 |
| cloudnull | hahahaha | 16:49 |
| b3rnard0 | #action git-harry help odyssey4me on blueprint https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration | 16:49 |
| b3rnard0 | anyone else? | 16:50 |
| b3rnard0 | okay let's move on then | 16:50 |
| cloudnull | last few min , BjoernT you want to hit on those bugs listed? | 16:50 |
| odyssey4me | The help would largely be to play devil's advocate. | 16:50 |
| b3rnard0 | skipping revews let's do the bugs | 16:50 |
| b3rnard0 | #topic Bugs | 16:50 |
| *** openstack changes topic to "Bugs (Meeting topic: OpenStack Ansible Meeting)" | 16:50 | |
| Apsu | cloudnull: The bugs are definitely lookers. They could use some BjoernT hitting-on | 16:50 |
| b3rnard0 | #link https://bugs.launchpad.net/openstack-ansible/+bug/1424808 | 16:51 |
| openstack | Launchpad bug 1424808 in openstack-ansible juno "Add nova configuration options image_cache_manager_interval" [Low,Triaged] - Assigned to Andy McCrae (andrew-mccrae) | 16:51 |
| odyssey4me | #link https://github.com/stackforge/os-ansible-deployment/blob/icehouse/rpc_deployment/vars/config_vars/keystone_config.yml | 16:51 |
| odyssey4me | #link https://github.com/stackforge/os-ansible-deployment/blob/icehouse/rpc_deployment/vars/config_vars/keystone_config.yml https://github.com/stackforge/os-ansible-deployment/blob/icehouse/rpc_deployment/roles/keystone_common/templates/template_gen | 16:51 |
| b3rnard0 | #link https://bugs.launchpad.net/openstack-ansible/+bug/1424971 | 16:51 |
| openstack | Launchpad bug 1424971 in openstack-ansible "ansible keystone module breaks with mixed case name" [Wishlist,New] | 16:51 |
| cloudnull | if not ill wishlist them | 16:51 |
| odyssey4me | sorry - just adding those for reference | 16:51 |
| b3rnard0 | odyssey4me: np | 16:51 |
| b3rnard0 | where did BjoernT go? | 16:51 |
| BjoernT | yeah I know what the background is on this one | 16:51 |
| BjoernT | I mean 1424971 charles requested that this one get's fixed but I think he didn't know it was caused by manual changes | 16:52 |
| cloudnull | imo this is someone made bad life choices and now we want a way to deal with those choices. | 16:52 |
| *** carl_baldwin has quit IRC | 16:52 | |
| BjoernT | so I would wait with this bug until I talked with everyone | 16:52 |
| *** salv-orlando has quit IRC | 16:53 | |
| *** kobis has quit IRC | 16:53 | |
| cloudnull | BjoernT: on https://bugs.launchpad.net/openstack-ansible/+bug/1424808 is that something you'd like to see in 10.1.3 ? | 16:53 |
| openstack | Launchpad bug 1424808 in openstack-ansible juno "Add nova configuration options image_cache_manager_interval" [Low,Triaged] - Assigned to Andy McCrae (andrew-mccrae) | 16:53 |
| BjoernT | 1424808 looks ok to me | 16:53 |
| BjoernT | yes 10.1.3 is ok | 16:54 |
| cloudnull | ^ b3rnard0 action item | 16:54 |
| cloudnull | any other open issue we want to talk about ? | 16:55 |
| *** ibiris_away is now known as ibiris | 16:55 | |
| b3rnard0 | #action andymccr to fix https://bugs.launchpad.net/openstack-ansible/+bug/1424808 in 10.1.3 | 16:55 |
| openstack | Launchpad bug 1424808 in openstack-ansible juno "Add nova configuration options image_cache_manager_interval" [Low,Triaged] - Assigned to Andy McCrae (andrew-mccrae) | 16:55 |
| *** aventerav has quit IRC | 16:55 | |
| *** bobmel has quit IRC | 16:55 | |
| b3rnard0 | #info BjoernT: I mean 1424971 charles requested that this one get's fixed but I think he didn't know it was caused by manual changes | 16:55 |
| *** aventerav has joined #openstack-meeting-4 | 16:56 | |
| b3rnard0 | #topic Open discussion | 16:56 |
| *** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)" | 16:56 | |
| *** bobmel has joined #openstack-meeting-4 | 16:56 | |
| cloudnull | ok lets call it. give everyone back a few mins. | 16:56 |
| Apsu | Woot, meeting rollover minutes! | 16:57 |
| cloudnull | thanks everyone . | 16:57 |
| Apsu | Good talk. | 16:57 |
| odyssey4me | :) | 16:57 |
| cloudnull | Apsu hahaha. | 16:57 |
| b3rnard0 | #endmeeting | 16:57 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:57 | |
| openstack | Meeting ended Thu Feb 26 16:57:21 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:57 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-26-16.02.html | 16:57 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-26-16.02.txt | 16:57 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-26-16.02.log.html | 16:57 |
| b3rnard0 | thanks everyone | 16:57 |
| palendae | Next meeting can go 4 minutes long | 16:57 |
| *** KLevenstein has left #openstack-meeting-4 | 16:57 | |
| *** odyssey4me has left #openstack-meeting-4 | 16:58 | |
| sigmavirus24 | heh | 17:00 |
| *** BjoernT has left #openstack-meeting-4 | 17:02 | |
| *** jckasper has joined #openstack-meeting-4 | 17:05 | |
| *** pkoniszewski has quit IRC | 17:07 | |
| *** jckasper_ has quit IRC | 17:09 | |
| *** prometheanfire has left #openstack-meeting-4 | 17:11 | |
| *** aventerav has quit IRC | 17:12 | |
| *** aventerav has joined #openstack-meeting-4 | 17:12 | |
| *** galstrom_zzz is now known as galstrom | 17:19 | |
| *** Sam-I-Am has left #openstack-meeting-4 | 17:21 | |
| *** belmoreira has quit IRC | 17:23 | |
| *** yamahata has joined #openstack-meeting-4 | 17:29 | |
| *** cloudnull has left #openstack-meeting-4 | 17:30 | |
| *** igordcard has quit IRC | 17:38 | |
| *** SumitNaiksatam has quit IRC | 17:40 | |
| *** b3rnard0 has left #openstack-meeting-4 | 17:40 | |
| *** git-harry has left #openstack-meeting-4 | 17:42 | |
| *** carl_baldwin has joined #openstack-meeting-4 | 17:45 | |
| *** evgenyf has quit IRC | 17:46 | |
| *** salv-orlando has joined #openstack-meeting-4 | 17:49 | |
| *** ibiris is now known as ibiris_away | 18:00 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 18:01 | |
| *** kbyrne has quit IRC | 18:03 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 18:03 | |
| *** emagana has joined #openstack-meeting-4 | 18:03 | |
| *** s3wong has joined #openstack-meeting-4 | 18:03 | |
| *** kbyrne has joined #openstack-meeting-4 | 18:05 | |
| *** SumitNaiksatam has quit IRC | 18:06 | |
| *** emagana has quit IRC | 18:07 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 18:07 | |
| *** stevelle has left #openstack-meeting-4 | 18:12 | |
| *** ChuckC has quit IRC | 18:17 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 18:18 | |
| *** VW_ has quit IRC | 18:20 | |
| *** VW_ has joined #openstack-meeting-4 | 18:20 | |
| *** pkoniszewski has joined #openstack-meeting-4 | 18:21 | |
| *** Aish has joined #openstack-meeting-4 | 18:22 | |
| *** jckasper has quit IRC | 18:32 | |
| *** erikmwilson has quit IRC | 18:38 | |
| *** ChuckC has joined #openstack-meeting-4 | 18:40 | |
| *** sbalukoff has quit IRC | 18:42 | |
| *** galstrom is now known as galstrom_zzz | 18:45 | |
| *** ChuckC has quit IRC | 18:47 | |
| *** ajmiller_ has joined #openstack-meeting-4 | 18:49 | |
| *** ChuckC has joined #openstack-meeting-4 | 18:49 | |
| *** ajmiller_ has quit IRC | 18:49 | |
| *** ajmiller_ has joined #openstack-meeting-4 | 18:50 | |
| *** kobis has joined #openstack-meeting-4 | 18:51 | |
| *** ajmiller has quit IRC | 18:52 | |
| *** galstrom_zzz is now known as galstrom | 18:58 | |
| *** numan has quit IRC | 19:06 | |
| *** ajmiller_ is now known as ajmiller | 19:07 | |
| *** pkoniszewski has quit IRC | 19:09 | |
| *** wojdev has joined #openstack-meeting-4 | 19:11 | |
| *** jckasper has joined #openstack-meeting-4 | 19:16 | |
| *** hareeshp has quit IRC | 19:28 | |
| *** matrohon has joined #openstack-meeting-4 | 19:32 | |
| *** s3wong has quit IRC | 19:32 | |
| *** s3wong has joined #openstack-meeting-4 | 19:33 | |
| *** wojdev has quit IRC | 19:45 | |
| *** wojdev has joined #openstack-meeting-4 | 19:46 | |
| *** sbalukoff has joined #openstack-meeting-4 | 19:47 | |
| *** VW_ has quit IRC | 20:02 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 20:32 | |
| *** hareeshp has joined #openstack-meeting-4 | 20:38 | |
| *** galstrom is now known as galstrom_zzz | 20:42 | |
| *** hareeshp has quit IRC | 20:49 | |
| *** galstrom_zzz is now known as galstrom | 20:51 | |
| *** hareeshp has joined #openstack-meeting-4 | 20:52 | |
| *** VW_ has joined #openstack-meeting-4 | 20:56 | |
| *** mwang2 has quit IRC | 21:02 | |
| *** rfolco has quit IRC | 21:03 | |
| *** mwang2 has joined #openstack-meeting-4 | 21:07 | |
| *** galstrom is now known as galstrom_zzz | 21:10 | |
| *** pkoniszewski has joined #openstack-meeting-4 | 21:34 | |
| *** galstrom_zzz is now known as galstrom | 21:36 | |
| *** pkonisze has joined #openstack-meeting-4 | 21:41 | |
| *** pkoniszewski has quit IRC | 21:44 | |
| *** banix has quit IRC | 21:46 | |
| *** banix has joined #openstack-meeting-4 | 21:47 | |
| *** markvoelker has quit IRC | 21:51 | |
| *** markvoelker has joined #openstack-meeting-4 | 21:51 | |
| *** markvoelker has quit IRC | 21:56 | |
| *** markvoelker has joined #openstack-meeting-4 | 21:57 | |
| *** banix has quit IRC | 22:16 | |
| *** VW_ has quit IRC | 22:16 | |
| *** VW_ has joined #openstack-meeting-4 | 22:17 | |
| *** notmyname has joined #openstack-meeting-4 | 22:23 | |
| *** hareeshp has quit IRC | 22:23 | |
| *** klamath has quit IRC | 22:50 | |
| *** matrohon has quit IRC | 22:51 | |
| *** pkonisze has quit IRC | 23:03 | |
| *** kobis has quit IRC | 23:09 | |
| *** IRTermite has quit IRC | 23:10 | |
| *** s3wong has quit IRC | 23:30 | |
| *** s3wong has joined #openstack-meeting-4 | 23:32 | |
| *** hareeshp has joined #openstack-meeting-4 | 23:32 | |
| *** mwang2_ has joined #openstack-meeting-4 | 23:41 | |
| *** mwang2 has quit IRC | 23:44 | |
| *** aventerav has quit IRC | 23:49 | |
| *** wojdev has quit IRC | 23:50 | |
| *** MarkAtwood has quit IRC | 23:55 | |
| *** galstrom is now known as galstrom_zzz | 23:57 | |
| *** salv-orlando has quit IRC | 23:57 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!
