Friday, 2015-01-30

*** TravT has quit IRC00:00
*** buzztroll has joined #openstack-glance00:03
*** buzztroll has quit IRC00:03
*** jgrimm is now known as zz_jgrimm00:09
*** nellysmitt has joined #openstack-glance00:09
*** ericpeterson has quit IRC00:12
*** nellysmitt has quit IRC00:14
*** jaypipes has joined #openstack-glance00:17
*** buzztroll has joined #openstack-glance00:23
*** buzztroll has quit IRC00:24
*** david-lyle is now known as david-lyle_afk00:31
*** jaypipes has quit IRC00:34
*** fifieldt has quit IRC01:00
*** annashen has quit IRC01:21
*** nellysmitt has joined #openstack-glance02:10
*** haomaiwa_ has joined #openstack-glance02:10
*** haomaiwa_ has quit IRC02:10
*** haomaiwang has joined #openstack-glance02:11
*** nellysmitt has quit IRC02:14
openstackgerrithzrandd proposed openstack/glance: Modify annotation information.  https://review.openstack.org/15112902:27
*** bkopilov has joined #openstack-glance02:30
openstackgerrithzrandd proposed openstack/glance: Modify annotation information.  https://review.openstack.org/15112902:32
*** rwsu is now known as rwsu-afk02:48
*** harlowja_ is now known as harlowja_away02:58
*** wayne___ has quit IRC03:27
*** adam_g_out is now known as adam_g03:29
*** cpallares has joined #openstack-glance03:31
*** buzztroll has joined #openstack-glance03:35
*** flwang has quit IRC03:37
*** buzztroll has quit IRC03:46
*** mtreinish_ has joined #openstack-glance03:47
*** annashen has joined #openstack-glance03:52
*** flwang has joined #openstack-glance03:52
*** takedakn has joined #openstack-glance03:54
*** mtreinish_ is now known as mtreinish04:04
*** annashen has quit IRC04:05
openstackgerrithzrandd proposed openstack/glance: Allow users to configure blacklist of URI schemes  https://review.openstack.org/15073604:09
*** nellysmitt has joined #openstack-glance04:11
*** spzala has quit IRC04:12
*** flwang has quit IRC04:12
*** nellysmitt has quit IRC04:15
*** buzztroll has joined #openstack-glance04:31
*** TravT has joined #openstack-glance04:43
*** annashen has joined #openstack-glance05:08
*** sigmavirus24 is now known as sigmavirus24_awa05:11
*** TravT has quit IRC05:11
*** ozialien has joined #openstack-glance05:12
*** annashen has quit IRC05:23
*** annashen has joined #openstack-glance05:24
*** buzztroll has quit IRC05:35
*** buzztroll has joined #openstack-glance05:38
*** buzztroll has quit IRC05:40
*** TravT has joined #openstack-glance05:40
*** buzztroll has joined #openstack-glance05:44
*** TravT has quit IRC05:46
*** echevemaster has quit IRC06:09
*** nellysmitt has joined #openstack-glance06:12
*** nellysmitt has quit IRC06:16
*** annashen has quit IRC06:21
openstackgerritOpenStack Proposal Bot proposed openstack/glance: Imported Translations from Transifex  https://review.openstack.org/14676506:22
*** annashen has joined #openstack-glance06:25
*** EmilienM is now known as EmilienM|afk06:29
*** buzztroll has quit IRC06:36
*** buzztroll has joined #openstack-glance06:39
*** annashen has quit IRC06:57
*** pkoniszewski has joined #openstack-glance07:08
openstackgerritAbhishek Kekane proposed openstack/glance: Eventlet green threads not released back to pool  https://review.openstack.org/13083907:14
*** belmoreira has joined #openstack-glance07:46
*** chlong has quit IRC08:08
*** groen692 has joined #openstack-glance08:08
*** nellysmitt has joined #openstack-glance08:13
*** nellysmitt has quit IRC08:14
*** nellysmitt has joined #openstack-glance08:14
*** takedakn has quit IRC08:17
*** markus_z has joined #openstack-glance08:41
*** buzztroll has quit IRC09:14
*** MattMan has quit IRC09:15
*** eglynn has joined #openstack-glance09:17
*** MattMan has joined #openstack-glance09:24
*** pdb has joined #openstack-glance09:31
*** jistr has joined #openstack-glance09:31
*** changbl has quit IRC10:01
*** sgotliv has joined #openstack-glance10:31
*** jamielennox is now known as jamielennox|away10:36
*** chlong has joined #openstack-glance10:43
*** jamielennox|away is now known as jamielennox10:44
*** pkoniszewski has quit IRC10:46
*** pkoniszewski has joined #openstack-glance10:46
*** krykowski has joined #openstack-glance10:46
*** nellysmitt has quit IRC10:50
*** krykowski has quit IRC10:55
*** jamielennox is now known as jamielennox|away10:56
*** buzztroll has joined #openstack-glance11:03
*** krykowski has joined #openstack-glance11:04
*** buzztroll has quit IRC11:08
*** krykowski has quit IRC11:25
*** krykowski has joined #openstack-glance11:26
*** aix has joined #openstack-glance11:34
*** diegows has joined #openstack-glance11:55
*** diegows has quit IRC11:55
*** diegows has joined #openstack-glance11:56
*** krykowski has quit IRC12:08
*** nellysmitt has joined #openstack-glance12:10
*** jasondotstar has quit IRC12:12
*** krykowski has joined #openstack-glance12:14
*** ozialien has quit IRC12:21
*** aix has quit IRC12:22
*** nellysmitt has quit IRC12:31
*** buzztroll has joined #openstack-glance12:52
*** krykowski has quit IRC12:56
*** buzztroll has quit IRC12:56
*** aix has joined #openstack-glance13:03
*** haomaiwang has quit IRC13:15
*** nellysmitt has joined #openstack-glance13:18
*** krykowski has joined #openstack-glance13:23
*** EmilienM|afk is now known as EmilienM13:28
*** jyoti-ranjan has joined #openstack-glance13:31
jyoti-ranjan I do have one qestion related to usage of swift for Glance data store13:31
jyoti-ranjan can I use swift which is not part of my cloud to configure it as a data store in my cloud?13:31
jyoti-ranjanAs per configuration:13:32
jyoti-ranjandefault_store = swift13:32
jyoti-ranjanswift_store_auth_address = $KEYSTONE_PROTOCOL://$KEYSTONE_HOST:$KEYSTONE_PORT/v2.0/13:32
jyoti-ranjanswift_store_user = $SERVICE_TENANT_NAME:glance13:32
jyoti-ranjanswift_store_key = $SERVICE_PASSWORD13:32
jyoti-ranjanswift_store_create_container_on_put = True13:32
jyoti-ranjanWhat is significance of swift_store_auth_address?13:32
kragnizjyoti-ranjan: that is the keystone server the swift user auths against13:32
kragnizie the keystone running on the cloud the swift cluster you want to use as a data store is part of13:33
jyoti-ranjanSo, if a user is part of cloud A which implicitly means keystone A. But swift is deployed in cloud B which has keystone B.13:33
jyoti-ranjanCan cloud A use keystone B (not of keystone A)?13:34
jyoti-ranjanGlance is expected to run in cloud A.13:34
kragnizthis is assuming glance is part of cloud A, you'll need a swift user on cloud B and point glance at cloud B's keystone address13:35
kragnizjyoti-ranjan: as far as I'm aware, that should work13:35
jyoti-ranjanyes13:36
*** tnurlygayanov has quit IRC13:41
*** changbl has joined #openstack-glance13:41
*** sigmavirus24_awa is now known as sigmavirus2413:50
*** jyoti-ranjan2 has joined #openstack-glance13:58
*** J_ has joined #openstack-glance14:04
*** krykowski has quit IRC14:08
*** eglynn is now known as eglynn-pto14:09
*** krykowski has joined #openstack-glance14:14
*** spzala has joined #openstack-glance14:15
*** jasondotstar has joined #openstack-glance14:15
*** sgotliv has quit IRC14:28
*** peristeri has joined #openstack-glance14:32
*** changbl has quit IRC14:33
*** EmilienM is now known as EmilienM|afl14:35
*** EmilienM|afl is now known as EmilienM|afk14:35
*** buzztroll has joined #openstack-glance14:40
*** buzztroll has quit IRC14:45
*** diegows has quit IRC14:53
*** zz_jgrimm is now known as jgrimm14:59
*** hemanth has joined #openstack-glance15:02
*** thangp has joined #openstack-glance15:10
*** sgotliv has joined #openstack-glance15:13
*** nellysmitt has quit IRC15:18
*** r-daneel has joined #openstack-glance15:22
*** vijendar has joined #openstack-glance15:35
*** pkoniszewski has quit IRC15:36
*** krykowski has quit IRC15:41
*** kragniz is now known as zingark15:53
openstackgerritIan Cordasco proposed openstack/glance: Pass a real image target to the policy enforcer  https://review.openstack.org/14665116:03
nikhil_kflwang1: hi16:04
sigmavirus24morning everyone16:04
nikhil_kmorning!16:05
nikhil_kPlease forgive my slow start today16:05
nikhil_kBack from a very long travel, close to 19hours yesterday16:05
sigmavirus24nikhil_k: i'll never forgive it =P16:05
sigmavirus24ativelkov: are you around by any chance?16:05
nikhil_kand around 16hrs on Monday :/16:05
ativelkovsigmavirus24: yup, I am, but heading to office in about 15 minutes16:06
sigmavirus24ativelkov: ping me when you get there =)16:06
zingark"I was a small mouse now" I do not understand16:06
zingarksigmavirus24: do you know what hzrandd means in that review?16:06
sigmavirus24zingark: I assume it was a google translate error.16:06
ativelkovsigmavirus24: ok16:06
zingarkah, I didn't think of that16:07
*** EmilienM|afk is now known as EmilienM16:07
sigmavirus24zingark: yeah I'm not bothered by it. I was confused at first but I'm pretty sure it isn't a big deal.16:07
sigmavirus24Also hzrandd seems to be the only person representing their company which I think is admirable16:07
* sigmavirus24 didn't realize that zingark is kragniz backwards at first16:08
zingarkI think there are a few other qq folk on other projects16:08
sigmavirus24"qq"?16:08
zingarkI may be mistaken, though16:08
zingarklike twitter but chinese16:09
sigmavirus24hzrandd was the only person who associated with them according to Stackalytics (which is obviously not a single source of truth)16:09
zingarkokay, that's cool then!16:09
sigmavirus24I think hzrandd is with NetEase, not qq16:09
zingarkI am a fool16:09
zingarkqq does an email service, too16:09
sigmavirus24No you just don't track people's associations down as methodically as I do16:10
sigmavirus24=P16:10
zingarkand he has his qq mail associated with gerrit16:10
zingark:P16:10
* sigmavirus24 could make joke about all the people with @gmail addresses but won't16:10
nikhil_ksigmavirus24: gunna go through the glance meeting logs, though do you know anything important for me to look into?16:10
*** belmoreira has quit IRC16:11
sigmavirus24nikhil_k: we didn't really talk about much because only 3 of us showed up16:12
sigmavirus24flaper87: wanted to discuss changes-since but no one else showed up so we didn't discuss it16:12
sigmavirus24We just looked at reviews and tricked flaper87 into approving things that had +2s ;)16:12
zingarkhe didn't fall for mine, though16:16
sigmavirus24He did catch on eventually16:17
zingarkaha, so he did!16:17
* zingark forgives flaper87 for ever doubting him16:17
sigmavirus24Oh and for people who missed the channel notice, zuul stopped working around 10:30 UTC and it seems fungi has given a proper kicking and is re-enqueueing jobs according to the logs that they captured16:19
*** david-lyle_afk is now known as david-lyle16:19
sigmavirus24tl;dr don't recheck unless you check Zuul to make sure your job is not in fact re-enqueued16:20
*** cpallares is now known as serallapc16:21
*** nellysmitt has joined #openstack-glance16:25
serallapcsigmavirus24: say your joke, say it!16:27
sigmavirus24why is everyone doing nick[::-1] today?16:29
*** buzztroll has joined #openstack-glance16:29
serallapcsigmavirus24: It's a trend zingark started in the raqaz channel.16:30
*** TravT has joined #openstack-glance16:30
* sigmavirus24 sighs16:33
zingarksigmavirus24: ti htiw og tsuj16:34
*** buzztroll has quit IRC16:34
sigmavirus24on16:35
*** TravT has quit IRC16:35
serallapczingark: yllej tsuj si 42surivamgis16:35
zingarkserallapc: setot16:36
*** jasondotstar has quit IRC16:36
*** buzztroll has joined #openstack-glance16:39
sigmavirus24setaogcm16:39
sigmavirus24setaogcm setot16:40
ativelkovsigmavirus24: o/16:42
sigmavirus24\o16:42
sigmavirus24So I'm wondering if we really need something as complex as SemVer when we have other standards we can use for version numbers16:42
*** jaypipes has joined #openstack-glance16:42
sigmavirus24(Especially ones with nearly identical sorting practices but simpler version strings)16:42
ativelkovwell, one of the reasons is because when I was designing Artifacts I was mostly thinking about Application Distribution16:44
sigmavirus24ativelkov: specifically, https://www.python.org/dev/peps/pep-0440/ is a standard around versioning of applications and distribution of them16:44
*** jyoti-ranjan has quit IRC16:45
ativelkovas far as I know, pep-440 is even more complicated then semver16:45
sigmavirus24It's one that has also heavily borrowed from other languages (like Ruby) and is rooted in real world usage (where as SemVer as I've seen it is less often used as fully as you are wishing to support it)16:45
*** jyoti-ranjan has joined #openstack-glance16:45
ativelkovsemver being its subset, I believe16:45
sigmavirus24ativelkov: you have it backwards16:45
sigmavirus24The only thing not in SemVer is epochs and those are still rather simple to support16:45
*** TravT has joined #openstack-glance16:46
sigmavirus24PEP-440 is far more restrictive16:46
ativelkovas far as I know, pbr uses a semver notation16:47
sigmavirus24also better defined (in my opinion) whereas SemVer is meant to encourage a greater deal of freedom that can lead to issues16:47
*** TravT has quit IRC16:47
sigmavirus24ativelkov: pbr is using PEP 440 because it has to be compatible with PEP 44016:47
sigmavirus24We may follow semver's release number prescriptions but pbr doesn't use the full spec of semver because it's specifically incompatible with PEP 44016:48
sigmavirus24Trust me, this was an issue when pip 6.0 was first released (because pbr was generating invalid version identifiers)16:48
*** TravT has joined #openstack-glance16:49
ativelkovhttps://github.com/openstack-dev/pbr/blob/master/doc/source/semver.rst16:49
*** rwsu-afk is now known as rwsu16:49
ativelkovi.e. their are adding git metadata to the pre-release labels16:50
sigmavirus24ativelkov: they *were* they don't16:51
sigmavirus24ativelkov: if they did that still every gate would be horribly broken16:51
ativelkovthere is some work in progress here: https://review.openstack.org/#/c/124651/16:52
ativelkovanyway, we don't have to follow them for the artifacts, but still, I tried to give the developers the most possible flexibility16:52
sigmavirus24So here's the thing, there's still a lot of flexibility in PEP440 and it would be simple enough for us to handle efficiently16:54
sigmavirus24There's also https://pypi.python.org/pypi/packaging16:54
sigmavirus24Which will parse those versions for us easily16:54
sigmavirus24It's the library pip uses16:54
ativelkovwell, it is fine, but PEP4404 is pythonic standard16:54
ativelkov440*16:55
ativelkovand semver is generic one16:55
sigmavirus24ativelkov: I'll reiterate, it's influenced by SemVer, real usage on PyPI, and the standards defined in other languages16:55
sigmavirus24It's a standard in Python land, but it's a standard that wasn't developed in a bubble and was made pragmatically16:55
ativelkovwell, I don't argue.16:56
ativelkovBut do we want, say, Java developers to learn it?16:56
sigmavirus24Java developers already learn new things while using OpenStack16:57
sigmavirus24Pretty much every consumer of openstack needs to learn new conventions to use it properly because so much of OpenStack already suffers from not-invented-here syndrome16:58
sigmavirus24I'd also argue it's easier to learn a narrowly defined specification than one so broadly defined with undefined behaviour16:58
ativelkovSure, but why increasing the amount of these new things? I mean, are there any reasons while we should use pep440 instead of semver?16:59
ativelkovAnd what is undefined in semver? I'd rather say it is extremely simple16:59
sigmavirus24ativelkov: I'm going to triple check but I'm rather certain that build information's affect on sorting isn't well defined for our purported usecase17:00
sigmavirus24ativelkov: SemVer is something that isn't a universal standard either17:01
sigmavirus24Most people use a fraction of it at best and that fraction that I've seen used is wholly compatible with PEP44017:01
ativelkovAccording to semver build metadata does NOT affect the precedence17:01
sigmavirus24I don't think people will be learning much of a new thing17:01
sigmavirus24ativelkov: and anyone familiar with operating system packages will think that's ridiculous17:02
sigmavirus24RHEL/CentOS/Debian/Arch/etc. all rely on build metadata for finding the most recently built version of the package17:02
ativelkov"Semantic versioning is a popular version identification scheme that is more prescriptive than this PEP regarding the significance of different elements of a release number."17:04
ativelkov(quote from the prp440 spec)17:05
ativelkovAnyway, I am fine with either of them17:05
ativelkovbut this still does not solve the main concern: how do we follow the right precedence in database17:06
nikhil_ksigmavirus24: thanks, for the input! (Was in a meeting, just back)17:06
ativelkovMy solution with long+string works for semver. Didn't check if it works for pep44017:06
*** zingark is now known as krangiz17:07
sigmavirus24ativelkov: PEP440 simplifies the potential structure of a version string. The database sorting can be solved similarly, we might just need to further restrict the max value for major/minor/patch versions17:07
*** krangiz is now known as kragniz17:07
ativelkovit seems it is a bit more complicated17:08
ativelkov1.0.dev4 should be less then 1.0.dev1017:08
ativelkovbut if we use plain ascii comparison it will not work17:08
sigmavirus24ativelkov: I'm not proposing we use plain ascii17:08
sigmavirus24In fact I think we can represent everything with the long-type17:08
*** ericpeterson has joined #openstack-glance17:10
ativelkovOk, I probably have to look deeper there17:11
ativelkovbut it really looks much more complicated then semver17:11
ativelkovtoo many entities17:12
ativelkovthey have this public version vs local version17:12
ativelkovfinal, pre and post-releases17:12
ativelkovdev releases17:12
ativelkovand epochs17:13
*** annashen has joined #openstack-glance17:13
ativelkov5 components of semver (where only 4 do really matter) seems much easier for me17:13
sigmavirus24So here's the problem I think we'll run into with semver though17:14
sigmavirus24We have version 1.10.11+companyA_2, 1.10.11+companyA_03, 1.10.11+companyB_3 that build metadata could really be pretty much anything and every user who sees it has to know exactly what it means to be able to understand what's being presented to them17:16
sigmavirus24there's a context that every user who sees that has to be able to have17:16
ativelkovright17:16
sigmavirus24The visual equivalent to that's effect on 440 versions though is defined17:17
ativelkovin 440 they have "local version" for that, right?17:17
sigmavirus24yeah and I'm just double checking my memory with the packaging package right now17:18
*** spzala has quit IRC17:18
*** spzala_ has joined #openstack-glance17:18
ativelkov"Comparison and ordering of local versions considers each segment of the local version (divided by a . ) separately. If a segment consists entirely of ASCII digits then that section should be considered an integer for comparison purposes and if a segment contains any ASCII letters than that segment is compared lexicographically with case insensitivity"17:18
*** spzala_ is now known as spzala17:18
ativelkovthat is exactly the same situation which semver has for their "pre-release labels" - and why I had to add string-based fields17:19
sigmavirus24https://gist.github.com/sigmavirus24/af5f6fb36c2d740a296a17:20
sigmavirus24except that it has no effect on sorting in SemVer which means we have no defined way of displaying it to the user17:21
sigmavirus24But yeah, that will make us have to add string fields which is what I was hoping to avoid17:21
ativelkovhttp://paste.openstack.org/show/164247/17:25
ativelkovabsolutely same result for semver17:25
ativelkovjust a bit different partitioning17:25
ativelkovin semver 10a10 becomes pre-release tag, openstack.1 becomes build meta17:25
ativelkovbut I see more serious problem in 44017:26
ativelkov(which is not a  real problem - it just indicates it is more powerfull - but it makes it much more complicated to store as a single long17:26
*** pdb has quit IRC17:26
ativelkovit has an arbitrary number of release components17:27
ativelkovsemver has just 3 of them17:27
ativelkovmajor-minor-patchs17:27
ativelkov440 is defined as N(.N)*17:27
ativelkovwhich means 1.2.3.4.5.6.7.817:28
ativelkovis perfectly fine17:28
sigmavirus24True17:28
sigmavirus24hm17:28
ativelkovso, if we want to have it stored as a single field we will have to assume some meaningful max value for number of segments and max value of each segment17:28
sigmavirus24version numbers are way too hard17:28
*** nellysmitt has quit IRC17:35
*** changbl has joined #openstack-glance17:39
*** spzala has quit IRC17:41
*** pennerc has joined #openstack-glance17:42
*** sgotliv has quit IRC17:45
*** pennerc_ has joined #openstack-glance17:45
*** jyoti_ranjan has joined #openstack-glance17:46
*** jyoti-ranjan has quit IRC17:46
*** jyoti-ranjan2 has quit IRC17:46
ativelkovsigmavirus24: just had a conversation with dims and jaypipes on that17:47
ativelkovdims confirms that their are using semver in pbr17:47
*** pennerc has quit IRC17:47
*** pennerc_ has quit IRC17:48
*** pennerc has joined #openstack-glance17:49
*** harlowja_away is now known as harlowja_17:50
*** jyoti_ranjan has quit IRC17:52
*** TravT_ has joined #openstack-glance17:52
*** TravT_ has quit IRC17:52
*** TravT has quit IRC17:52
*** alex_xu has quit IRC17:52
sigmavirus24ativelkov: where did you have that discussion? I am certain they're incorrect. It's the reason setuptools 8 and pip 6 were blocked for quite a while17:53
sigmavirus24They're using at best the subset of semver that is compatible with pep44017:53
ativelkovJust here at the office :)17:54
sigmavirus24ativelkov: I know we're also using the roles defined for major/minor/patch but the version strings generated are PEP 440 strings17:54
ativelkovwe may ask dims to join us in this conversation17:55
sigmavirus24Previously the strings included the git SHA in a 440 incompatible way17:55
sigmavirus24dhellmann: is here too17:55
*** alex_xu has joined #openstack-glance17:55
sigmavirus24They could be including that in the local identifier though17:55
sigmavirus24hm17:55
* sigmavirus24 checks published packages17:55
ativelkovThat may be, right17:55
sigmavirus24There previously doing things like 0.15.0.<sha>17:55
sigmavirus24which broke with pip 6/setuptools 817:56
sigmavirus24They could be doing 0.15.0+<gitsha>17:56
ativelkovAnyway, the more important thing is that artifacts should be necessary be pbr-compatible: this is thing which is quite external for openstack17:56
sigmavirus24Why do they need to be pbr compatible?17:56
ativelkovand even for python17:56
*** pennerc has quit IRC17:56
ativelkovsorry, should NOT be17:56
sigmavirus24ativelkov: so here's the thing, users are defining these strings for version identifiers right?17:57
ativelkovyes17:57
ativelkovso this is actually part of the API17:57
sigmavirus24Right, but (unlike pbr) these versions aren't machine generated/internal17:58
ativelkovsome of them may be17:58
sigmavirus24I think I'm wondering why we're restricting users at all17:58
ativelkovi.e. there may be a CI-CD system which publishes its artifacts in Glance17:58
*** hemanth has quit IRC17:58
sigmavirus24ativelkov: sure17:59
sigmavirus24but these are still arbitrary version identifiers chosen by the user and eventually principally consumed by the user17:59
ativelkovbecause we need to have a precedence defined17:59
*** J_ has quit IRC17:59
ativelkovsay, there should be a qury "give me the latest version of artifact with the name=X and type=Z"18:00
ativelkovalso, there will be a "clone-and-bump-the-version" operation18:00
ativelkovso, we have to define the logic for that unambiguously18:01
ativelkovif the version is just some meaningless string, then we won't be able to do so18:01
sigmavirus24you realize then that the most practical way of doing this is by using dates, right?18:01
ativelkovdates is just one of the way of doing that18:02
*** eglynn-pto has quit IRC18:02
ativelkovthat's why there exist an obvious mapping of the date to semver18:02
sigmavirus24ativelkov: so let me ask you this18:02
*** spzala has joined #openstack-glance18:03
sigmavirus24let's say there are versions 1.2.3, and 1.2.4 in the database already18:03
sigmavirus24the user says "clone 1.2.3 and bump the patch versioN"18:03
sigmavirus24what should they get?18:03
ativelkovan exception18:03
sigmavirus24or will that only ever be "clone and bump the latest"18:03
sigmavirus24So why can't they clone 1.2.3 and fork it?18:04
ativelkovthey may, if they specify the name explicitly18:04
ativelkovsay, clone 1.2.3 and for it to 1.2.3-my-revision18:04
ativelkovand fork* it18:04
*** harlowja_ has quit IRC18:04
ativelkovthen it works18:04
*** julim has quit IRC18:05
sigmavirus24ativelkov: some services I can think of would bump the version as 1.2.4+118:05
*** julim has joined #openstack-glance18:06
*** eglynn-pto has joined #openstack-glance18:06
sigmavirus24seems like something that's going to happen, raising an exception becomes user-hostile at that point18:06
sigmavirus24they then have to learn how glance is storing the version and providing this other functionality for them18:06
*** harlowja has joined #openstack-glance18:07
*** annashen has quit IRC18:08
sigmavirus24I'm just trying to wrap my head around all of this artifacts stuff and I totally understand the desire to sort all of this in the database. I 100% agree but I don't see the use case for sorting it in terms of latest where created_at wouldn't be as accurate if not more accurate18:08
*** mfedosin has quit IRC18:08
*** Guest35467 has quit IRC18:09
*** alex_xu has quit IRC18:09
*** hemanth has joined #openstack-glance18:10
*** alex_xu has joined #openstack-glance18:11
*** spzala has quit IRC18:12
ativelkovsigmavirus24: imaging you ar eimporting arttifacts from remote source18:12
ativelkovi.e. just uploading files with all the metadata embedded18:13
ativelkovcreated_at will actually mean the timestamp of the import operation18:13
ativelkovwhile version denotes the version (and so most probably the creaion order of the artifact itself)18:14
*** pennerc has joined #openstack-glance18:14
ativelkovnot to speak that you may have 1.0 and 2.0 and then maintain both branches, so you will add 2.1 and then 1.1, so created_at order will give you 1.0, 2.0, 2.1, 1.1, which is definetely different from the version order18:15
*** markus_z has quit IRC18:17
*** annashen has joined #openstack-glance18:17
*** mfedosin has joined #openstack-glance18:20
openstackgerritInessa Vasilevskaya proposed openstack/glance: Artifacts API  https://review.openstack.org/13662918:25
*** plaurin_ has joined #openstack-glance18:28
*** serallapc is now known as cpallares18:29
ativelkovsigmavirus24: checked that with dims: they call it "semantic version" but that is indeed pep44018:29
plaurin_hello everyone. I have a question. Is there a way to use glance outside of the controller node (a different server than keystone)? And also, is the api-paste config file still in use in the juno release?18:30
nikhil_kYes and yes, plaurin_18:32
plaurin_(I understand that it's possible configuring the endpoints for remote servers, but I failed to do so, having connection refused issues)18:32
plaurin_nikhil_k: Thanks. In the juno docs (for Ubuntu) there's nothing about the api-paste config file like there use to be in the previous releases.18:33
plaurin_http://docs.openstack.org/juno/install-guide/install/apt/content/glance-install.html18:34
plaurin_nothing about api-paste files like in the havana release18:35
plaurin_Maybe that's why I can't connect to keystone, I did not fill the api paste files.18:38
*** jaypipes has quit IRC18:45
*** jaypipes has joined #openstack-glance18:49
*** jaypipes is now known as leakypipes18:50
*** MattMan has left #openstack-glance18:52
sigmavirus24ativelkov: good point on the created_at bit. It's been a lot longer since I read the original Artifacts spec so I'm re-reading that now to see if that helps me figure out better what needs to be supported18:53
sigmavirus24ativelkov: also, yeah, you can munge 440 and SemVer together if you only use major/minor/patch and use the semantics around their meanings18:54
nikhil_kplaurin_: hmm, thanks for bringing that up! Mind opening a bug for juno, icehouse, master. This kind of falls under glance and documentation shared category so, we may have to check with annegentle on this.18:57
ativelkovsigmavirus24: yes, they definetely have a common subset.18:58
sigmavirus24nikhil_k: btw, you told me to remind you about being added to the drivers team on LaunchPad (same for flaper87 I suppose)18:59
sigmavirus24be back shorlty18:59
nikhil_ksigmavirus24: ah yes, still waiting to hear back from Mark18:59
nikhil_kthanks for reminder!18:59
sigmavirus24My calendar deserves all the praise =P18:59
nikhil_k;)19:00
ativelkovnikhil_k: btw, what about the expansion of the core team? You wanted to postpone it till the mini-summit, but it turned out we didn't discuss it then (or did I miss something?)19:02
plaurin_nikhil_k: Sure, I'll open a bug later today19:04
*** jistr has quit IRC19:08
*** jasondotstar has joined #openstack-glance19:10
nikhil_kplaurin_: thanks!19:14
nikhil_kativelkov: yeah, the mini-summit turned out to be longer than expected and we did not get to discuss a few items like19:14
nikhil_kreview guidelines, core memberships and changes-since filters19:15
nikhil_ktbh, I am a little worried about adding more cores to that program where the existing merges are being an issue for the gate, release management, stability etc19:16
nikhil_kHope that helps!19:17
*** pennerc has quit IRC19:20
*** flwang has joined #openstack-glance19:23
stevelleanyone here able to tell me they work on glance in a devstack environment?19:23
*** zul has quit IRC19:24
*** zul has joined #openstack-glance19:27
*** pennerc has joined #openstack-glance19:29
kragnizstevelle: I work on glance in a devstack enviroment19:29
kragnizI'm not quite sure if that's what you were asking, though :P19:29
stevellekragniz: I think it is19:29
stevelleI am struggling badly with keeping a development environment for glance happy19:30
stevellekragniz: do you just rebuild your devstack from scratch regularly?19:30
kragnizstevelle: not very often19:31
kragnizI'm not sure when I last rebuilt, but it was a few weeks ago19:32
*** nellysmitt has joined #openstack-glance19:35
nikhil_kstevelle: what's broken again?19:36
nikhil_k:/19:36
stevellethe Registry doesn't start when running tests19:36
nikhil_koh that19:37
nikhil_kstill?19:37
sigmavirus24stevelle: that's odd19:37
stevelleI had stuff working in a devenv for a little while but now it's broken again after this week's changes to master19:37
stevellethe only thing that ever worked for me to get the registry to start up in tests was to not use a virtualenv19:38
sigmavirus24stevelle: I saw that earlier this week but rebased my patchset and now it seems to be working okay19:38
sigmavirus24let me rebase again19:38
stevelleI'm trying to test my rebase of https://review.openstack.org/#/c/148400/ before I send into review again19:39
*** nellysmitt has quit IRC19:40
* sigmavirus24 is running the tests19:40
*** spzala has joined #openstack-glance19:45
*** EmilienM is now known as EmilienM|afk19:47
*** spzala has quit IRC19:49
nikhil_kwell a 12.09pm (EST) jenkins run shows green -> https://review.openstack.org/#/c/149759/19:50
* nikhil_k not worried about the gate anymore19:50
sigmavirus24stevelle: no worries forme19:53
sigmavirus24woo backports19:53
stevelleIt would help a lot if I knew how to diagnose why registry isn't working but I'm boarding a plane in a few minutes.19:55
stevellewill poke at this more later19:55
kragnizstevelle: safe flight19:55
nikhil_kstevelle: cool, have a good one. Do you not work out of bay area?19:56
nikhil_kstevelle: run19:56
nikhil_krun_tests.log might be your best friend btw19:56
stevellenikhil_k: I live north of bay area19:57
nikhil_kah19:58
stevellealso, run_tests.log only says that registry was expected to start.  no errors from registry itself because it is forked.19:58
sigmavirus24stevelle: are you getting a mismatch in return code?19:58
stevellesigmavirus24: no, the only clue is that "expected registry started True was False19:58
sigmavirus24you might also want to make sure there isn't a zombie registry still bound to that port19:58
sigmavirus24lsof -i19:58
stevelleno zombies, already checked that19:59
nikhil_kyeah, that test does not seem to touch registry19:59
*** aix has quit IRC19:59
nikhil_kkragniz: while I have you here, currently gunna check your spec https://blueprints.launchpad.net/glance/+spec/swift-retry-wait20:01
nikhil_kkragniz: do you have any pending feedback (from anyone) that I may not be aware of20:01
nikhil_kheard a few comments in hallway conversations during the mini-summit about it20:02
kragniznikhil_k: waiting to talk to stuart about it20:02
kragniznikhil_k: I haven't spoken with him since the midcycle20:02
kragnizanything interesting in the hallway conversations?20:03
nikhil_kpeople not being happy with the defaults being increased20:04
kragnizokay20:04
*** openstackgerrit has quit IRC20:06
*** openstackgerrit has joined #openstack-glance20:06
nikhil_kkragniz: if it gets a bit more delayed then we need to merge it (soon) after k220:07
nikhil_kas it has a some of the reviews against Glance20:07
kragnizof course20:07
kragnizI'm feeling using the current defaults is okay20:08
kragnizI'd like to hear what stuart thinks, though20:08
kragnizyou guys have mostly persuaded me :P20:09
nikhil_kheh20:10
nikhil_kI'm neutral on this as we've our own setup of the defaults20:11
nikhil_khowever, it would be good to have some feedback from the people who use the Glance defaults20:11
*** spzala has joined #openstack-glance20:11
kragnizindeed20:11
nikhil_kbtw, glad to see your oslo namespace changes merged https://review.openstack.org/#/q/status:merged+project:openstack/glance+branch:master+topic:bp/drop-namespace-packages,n,z20:11
kragniznikhil_k: https://review.openstack.org/#/q/project:openstack/python-glanceclient+branch:master+topic:bp/drop-namespace-packages,n,z20:12
kragniz:P20:12
nikhil_kyeah20:12
nikhil_kI was looking at why zhiyan did not +A https://review.openstack.org/#/c/145799/20:12
nikhil_kThey are _relatively_ smaller than glance related ones20:13
kragniznikhil_k: I think because the patch it depends on wasn't merged20:13
nikhil_kand now it's outdated ?20:13
kragnizyeah20:13
kragnizneed to rebase that20:14
nikhil_kcool20:14
nikhil_kanyone +A that should start auto merge after the dependency merged20:14
nikhil_kmerges*20:14
*** groen692 has quit IRC20:14
kragnizI'm working on porting to oslo_log in glance, too20:15
nikhil_kok nice20:15
nikhil_kwould suggest waiting until after k220:15
kragnizon that matter, any thoughts on https://github.com/openstack/glance/blob/master/glance/opts.py?20:15
kragnizyeah, it's going to take a bit of time20:15
kragnizglance.openstack.common.log.common_cli_opts isn't public anymore20:16
kragnizand this file was only added for use with oslo-config-generator20:16
nikhil_keh20:17
nikhil_kdo you have the commit which removed the module from public ns20:18
nikhil_k?20:18
*** pennerc has quit IRC20:18
kragniznikhil_k: that happened a bit before the module moved out of the oslo incubator20:18
kragnizI'll have a dig20:19
nikhil_kok, no worries20:19
kragniznova and cinder both pick up those extra options from a config file20:21
kragnizhttps://github.com/openstack/nova/blob/master/tools/config/oslo.config.generator.rc20:21
*** flwang has quit IRC20:24
nikhil_kkragniz: guessing even the logging opts are not global anymore?20:24
kragniznikhil_k: yeah20:24
*** david-lyle has quit IRC20:25
nikhil_kthat mechanism looks fine, though is kinda fragile adding dependencies in a remote file in a list!20:25
sigmavirus24nikhil_k: I'm thinking we should abandon https://review.openstack.org/#/c/145796/ (moving stuff around in config files on stable/* seems like a bad idea)20:26
nikhil_kkragniz: as long as we can have tests around this20:26
kragniznikhil_k: I know!20:26
nikhil_ksigmavirus24: yeah may be, though it would be great to have stuff consistent :P20:28
dhellmannnikhil_k, kragniz : the new oslo config generator in oslo.config lets you include options from libraries, too: http://docs.openstack.org/developer/oslo.config/generator.html20:28
kragnizsigmavirus24: +1 to that20:28
sigmavirus24kragniz: +1 to abandonment?20:29
*** harlowja is now known as harlowja_away20:29
kragnizdhellmann: cool!20:30
kragniz(should probably have read the documentation...)20:30
kragnizdhellmann saves the day again20:30
kragnizsigmavirus24: yes20:31
openstackgerritSarvesh Ranjan proposed openstack/glance: Typos fixed in the comments  https://review.openstack.org/15176420:31
kragniznikhil_k: in that case, we really don't need glance/opts.py20:33
sigmavirus24kragniz: git rm glance/opts.py ; ./run_tests.sh && git commit -m 'FIXED IT' && git review20:34
*** harlowja_away is now known as harlowja20:34
openstackgerritAlexander Tivelkov proposed openstack/glance-specs: Semver Utility for DB storage  https://review.openstack.org/13959520:34
nikhil_kkragniz: dhellmann : that looks awesome!20:34
nikhil_kyeah, we do not need it20:34
kragnizsigmavirus24: sounds good!20:35
dhellmannnikhil_k: oslo is full of awesome ;-)20:35
nikhil_kheh :)20:35
kragnizdhellmann: the magic just keeps coming20:35
sigmavirus24kragniz: project idea for this weekend: oslo-magic-generator ;)20:36
kragnizsigmavirus24: does that generate oslo code?20:37
openstackgerritIan Cordasco proposed openstack/glance: Pass a real image target to the policy enforcer  https://review.openstack.org/14665120:37
*** eglynn-pto has quit IRC20:39
openstackgerritAlexander Tivelkov proposed openstack/glance-specs: Semver Utility for DB storage  https://review.openstack.org/13959520:40
nikhil_ksigmavirus24: what was the consensus about the SemVer stuff?20:40
nikhil_kseems like we need a wrapper around the python library20:41
nikhil_k?20:41
ativelkovnikhil_k: I've just updated the spec to address that20:41
nikhil_kativelkov: awesome, thanks!20:41
ativelkovand answer most of the other question sigmavirus24 and kragniz had20:41
nikhil_kwanted to get first level feedback around the major concerns20:41
ativelkovAs far as I can see, the main issue is semver vs PEP440 topic20:42
kragnizsigmavirus24: probably a silly question, but is there a pep440 library like python-semanticversion?20:45
ativelkovkragniz: yes. It is called pbr :)20:46
ativelkovjust "import pbr.version"20:46
kragnizhmm20:47
kragnizokay20:47
ativelkovthat is not perfect solution, as it more targets the package version info, and so has some specifics, but it still may be used to check the differences between semver and pep44020:48
sigmavirus24kragniz: no the actual one is packaging20:48
sigmavirus24PBR is just already in the global-requirements20:48
kragnizright, that makes sense20:48
sigmavirus24packaging carries the official implementation of pep44020:49
sigmavirus24it's what pip uses too20:49
ativelkovah, yes, thanks sigmavirus2420:49
sigmavirus24no worries20:49
sigmavirus24being a pypa member makes me more aware of these things sadly20:49
kragnizsigmavirus24: I should have been watching my github feed more closely, since you folked that a few hours ago :P20:49
sigmavirus24oh yeah that was because the description.rst on PyPI is rendering funny20:50
sigmavirus24and I know how to fix those all too damned well20:50
kragnizheh20:51
kragnizsigmavirus24: btw20:52
kragnizsigmavirus24: there's still time for you to come to fosdem20:52
sigmavirus24when is it?20:52
kragniztomorrow20:52
kragniztotally enough time to fly over20:52
sigmavirus24no thanks20:52
sigmavirus24=P20:52
kragnizgo on20:52
sigmavirus24if you see Tarék though say hi20:52
sigmavirus24tell him you love all the work he still puts into Flake8 =P20:53
kragnizI will do :P20:53
kragnizdo you know if he's giving a talk this year?20:53
sigmavirus24then ask him why he uses a go board for a gravatar =P20:53
sigmavirus24Not the slightest. I haven't spoken to him in over a year20:54
kragnizheh20:54
kragnizokay20:54
kragnizsigmavirus24: why do you have a three in a row board as your avatar?20:55
sigmavirus24you mean bingo card?20:55
sigmavirus24also I can' tell you how depressing it is when programmers don't know what conway's game of life is20:56
stevellewhat's that?  is it on PS4? :D20:56
kragnizstevelle: it's a great game, but the graphics are a little dated20:57
sigmavirus24stevelle: <320:57
*** eglynn-pto has joined #openstack-glance20:59
*** pennerc has joined #openstack-glance21:00
*** pennerc has quit IRC21:05
kragniznikhil_k: do we want to do glance client release mid next week?21:12
*** sigmavirus24 is now known as sigmavirus24_awa21:13
nikhil_kkragniz: after the release, yes21:13
* nikhil_k needs to check the update on capabilities spec21:13
kragnizokay21:13
kragnizwe should start merging some patchsets, there's quite a backlog of simple fixes21:15
kragnizhttps://review.openstack.org/#/q/status:open+project:openstack/python-glanceclient,n,z21:15
*** sigmavirus24_awa is now known as sigmavirus2421:18
*** leakypipes has quit IRC21:20
*** mjturek has quit IRC21:21
nikhil_klet's focus on k2 until mid next week21:24
nikhil_khttps://launchpad.net/glance/+milestone/kilo-221:24
kragnizdidn't we say the same around k1? :P21:26
sigmavirus24nikhil_k: thoughts on https://review.openstack.org/#/c/148387/ ?21:27
nikhil_kif you care about some specific ones, feel free to bring them up21:27
nikhil_kthe whole point of release management is to ensure that we help reviewers keep focus21:27
*** thangp has quit IRC21:28
nikhil_ksigmavirus24: looks like a good addition21:30
*** nellysmitt has joined #openstack-glance21:36
*** nellysmitt has quit IRC21:41
sigmavirus24nikhil_k: https://review.openstack.org/#/c/148574/ seems ready for approval =P21:47
nikhil_ksg21:49
*** jgrimm is now known as zz_jgrimm21:52
sigmavirus24nikhil_k: or review from you more accurately21:54
nikhil_ksigmavirus24: it's on my agenda21:55
nikhil_kjust want to focus on specs first as they can be blockers for the code21:55
sigmavirus24yeah just realized it sounded like I was trying to get you to do a +W without reviewing =P21:55
*** jasondotstar has quit IRC21:56
*** pkoniszewski has joined #openstack-glance21:56
nikhil_kheh, ok21:58
nikhil_kI need to put on the reviewing gear on21:58
nikhil_ks/put on/put/21:58
*** cpallares has quit IRC22:03
*** pkoniszewski has quit IRC22:03
*** ericpeterson has quit IRC22:07
*** peristeri has quit IRC22:11
*** TravT has joined #openstack-glance22:31
*** leakypipes has joined #openstack-glance22:40
nikhil_ksigmavirus24: see a ton of -1s on this https://review.openstack.org/#/c/139726/22:41
nikhil_kand on the spec, not so much22:41
sigmavirus24Yeah there was confusion22:41
nikhil_kalthough, I'm just catching up and have not read the whole thing including all comments22:42
sigmavirus24zhiyan: has a good point that there needs to be a corresponding change to glance for etc/ and doc/. Erno was worried about backwards compat22:42
sigmavirus24s/Erno/jokke_/22:42
openstackgerritMerged openstack/glance-specs: Spec to replace snet config with endpoint config  https://review.openstack.org/14697222:59
*** tellesnobrega has quit IRC23:03
*** harlowja is now known as harlowja_away23:05
*** jasondotstar has joined #openstack-glance23:05
*** jasondotstar has quit IRC23:05
nikhil_ksigmavirus24: heh, should have read your message before reading the whole conversation ;)23:06
nikhil_kthanks though!23:06
sigmavirus24nikhil_k: I probably should have pinged you while explaining it =P23:06
*** leakypipes has quit IRC23:10
*** harlowja_away is now known as harlowja23:27
*** harlowja has quit IRC23:29
*** harlowja has joined #openstack-glance23:29
*** leakypipes has joined #openstack-glance23:32
*** nellysmitt has joined #openstack-glance23:37
*** vijendar has quit IRC23:40
*** nellysmitt has quit IRC23:42
*** annashen has quit IRC23:57
*** changbl has quit IRC23:58
openstackgerritIan Cordasco proposed openstack/glance: Pass a real image target to the policy enforcer  https://review.openstack.org/14665123:58

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