Wednesday, 2015-07-15

*** david-lyle has quit IRC00:25
*** dims__ has quit IRC00:54
*** dims_ has joined #openstack-relmgr-office01:28
*** david-lyle has joined #openstack-relmgr-office02:12
*** dims_ has quit IRC02:17
*** david-lyle has quit IRC02:35
*** dims_ has joined #openstack-relmgr-office03:19
*** dims_ has quit IRC03:23
*** david-lyle has joined #openstack-relmgr-office03:38
*** cfriesen has left #openstack-relmgr-office04:27
*** dims_ has joined #openstack-relmgr-office07:20
*** dims_ has quit IRC07:26
*** Kiall has quit IRC07:26
*** Kiall has joined #openstack-relmgr-office07:28
*** dims_ has joined #openstack-relmgr-office10:03
*** dims_ has quit IRC10:05
*** openstack has joined #openstack-relmgr-office11:38
*** openstackstatus has joined #openstack-relmgr-office11:38
*** ChanServ sets mode: +v openstackstatus11:38
*** dims_ has joined #openstack-relmgr-office11:47
ttxdhellmann: we actually have nobody with +2 in openstack/releases yet :)12:16
*** dims_ has quit IRC12:41
*** bnemec has joined #openstack-relmgr-office12:41
dhellmannttx: ugh, I forgot a step :-)12:55
ttxdhellmann: let me know when you have 5 minutes so that we finalize the talk submission12:59
dhellmannttx: now is good fo rme13:00
ttxok13:00
ttxI'll pm13:00
*** dims_ has joined #openstack-relmgr-office13:06
SergeyLukjanovttx, dhellmann, hey13:21
SergeyLukjanovwe need to backport few features support in saharaclient (their support was added in Sahara, but we missed corresponding CRs in client due to the switch to the stable branches model in client)13:22
SergeyLukjanovas we have a next major version used in master already, is it okay to backport this features support to the stable/kilo client branch and release next minor version? all changes are backward compat, just adding support for the new propoerties13:23
SergeyLukjanovotherwise the "official" Kilo client will not support some sahara features introduced in KIlo13:24
SergeyLukjanovttx, dhellmann, ^^13:24
dhellmannSergeyLukjanov: hmm13:26
dhellmannSergeyLukjanov: how many features are we talking about?13:27
SergeyLukjanovactually the stable/kilo branch was created too early == from incorrect commit and due to the old model all testing we were doing was done using the fresh code from master13:27
SergeyLukjanovdhellmann, 2-313:27
ttxso the trick is that we can't bump Y13:28
dhellmannyeah13:28
SergeyLukjanovyup13:28
ttxany reason why users can't use the "liberty" version ? I think they are supposed to use that one anyway by default ?13:29
SergeyLukjanovttx, dependencies13:29
ttxi.e. the stable branch one is more a corner case than the recommended version ?13:29
dhellmannright, the stable branch releases are meant for use when one server talks to another, users should be able to install the latest client and talk to a service13:30
SergeyLukjanovttx, if somebody installs OpenStack from packages then the correct package should be used13:30
SergeyLukjanovI mean correct == with kilo dependecies13:30
ttxSergeyLukjanov: I can see how that affects server usage of python-saharaclient, but I doubt that servers need access to those features ?13:31
ttxhuman users can/should install the latest and talk to a kilo host, no ?13:31
SergeyLukjanovttx, hm, that's true, but IMO from users PoV if you want to install client that will correctly work with the Kilo OpenStack that stable/kilo client branch should be used13:33
SergeyLukjanovas we have this stable/kilo branch introduced13:33
SergeyLukjanovservers not really affected as corresponding changes wasn't merged into horizon (you know, it takes months to have something merged into horizon)13:34
dhellmannexcept that's not what the branch is for13:34
SergeyLukjanovI understand13:34
ttxI mean, I agree that it's /better/ if the stable/kilo branch is fully usable with the kilo version13:35
ttxthe question is, it it worth breaking semver for that13:35
ttxI think saying "if you want to acces sthose features you need >=1.3.14 is acceptable13:36
dhellmannwe could treat these as bugs introduced by the way we created the branch, like we did with the dependency caps13:36
SergeyLukjanovso, you think that we should just ignore it and say that stable/kilo client branch is just for the cross server communication and if the features needed then liberty versions should be used13:36
ttxall depends how central are those features I guess13:36
ttxthe latest version should always be used13:36
ttxif you can't work or a critical function is missing I guess we could consider it a bug13:37
SergeyLukjanovokay...13:37
ttxit's a bit of a grey area, depending on what's actually missing13:37
SergeyLukjanovI'm just trying to look on it from the distros PoV and I think all distros was using clients released "near" the OpenStack release and now will use clients from stable/kilo to have the same dependencies13:38
dhellmannttx: mordred put me in the releases-core group, and I've added the library-releases and "Release Managers" groups13:38
SergeyLukjanovttx, it's not a show blocker features, but useful - support for the volumes to instances locality and event log for proisioning13:39
dhellmannSergeyLukjanov: yes, that's expected for packages to deploy the cloud13:39
dhellmannttx: https://review.openstack.org/#/admin/groups/977,members13:40
SergeyLukjanovokay, so, let's keep it as is13:40
dhellmannSergeyLukjanov: ok. if it becomes a serious problem, we can discuss it again, but I think it's safest to be conservative about backports13:41
ttxSergeyLukjanov: I'd communicate about the new version in liberty that gives access to those features, and encourage kilo users to use that13:41
ttxit's not as if everyone would have magically switched to that new stable/kilo version anyway, so communication is key13:42
ttxdhellmann: ok, all approved13:47
openstackgerritMerged openstack/releases: tox setup  https://review.openstack.org/19810513:49
openstackgerritMerged openstack/releases: Add README file  https://review.openstack.org/19804113:49
openstackgerritMerged openstack/releases: Add old deliverable files  https://review.openstack.org/19810613:49
*** sigmavirus24_awa is now known as sigmavirus2414:12
dhellmannttx: if you have some time, there are a few release-tools changes pending that could use reviews. dims +1ed several already14:44
ttxack, still catching up14:53
openstackgerritMerged openstack-infra/release-tools: clean up repodir handling  https://review.openstack.org/20074015:38
openstackgerritMerged openstack-infra/release-tools: don't assume all projects are in the openstack namespace  https://review.openstack.org/20074115:38
openstackgerritMerged openstack-infra/release-tools: use more efficient query to find milestone  https://review.openstack.org/20127415:39
*** ig0r__ has quit IRC15:39
*** ig0r_ has joined #openstack-relmgr-office15:40
dhellmannnotmyname: when you're ready to talk about the swift client release, see http://lists.openstack.org/pipermail/openstack-dev/2015-July/069603.html first and then let me know16:00
dhellmanndims_: it would be good for us to start recording the oslo releases in the new release repo following the new process from http://lists.openstack.org/pipermail/openstack-dev/2015-July/069603.html -- we should think about some tools to make updating those files simpler16:01
notmynamedhellmann: I'm in some meetings this morning. I'll ping you later16:02
dhellmannnotmyname: sure, no hurry16:02
dims_dhellmann: ack, will read the link in a bit (in keystone mid-cycle)16:06
dhellmanndims_: k16:06
openstackgerritDoug Hellmann proposed openstack/releases: oslotest 1.5.2  https://review.openstack.org/20217716:25
*** sigmavirus24 is now known as sigmavirus24_awa17:10
*** pabelanger has joined #openstack-relmgr-office17:24
*** sigmavirus24_awa is now known as sigmavirus2418:06
*** EmilienM has joined #openstack-relmgr-office18:14
EmilienMdhellmann: got a question about releases. Puppet modules have been released last week (6.0.0 which is our first stable/kilo). Should I submit a YAML file to http://git.openstack.org/cgit/openstack/releases/tree/README.rst ?18:18
EmilienMor should I submit a YAML next time we plan to do a release18:19
dhellmannEmilienM: is the release team managing those releases for you?18:21
EmilienMdhellmann: nope18:21
dhellmannEmilienM: ok, then for now you don't need to worry about the release repo -- we're going to get it set up for the managed projects first18:22
EmilienMdhellmann: ack18:22
EmilienMthanks!18:22
dhellmannEmilienM: any time, thanks for checking18:24
*** EmilienM has left #openstack-relmgr-office18:25
openstackgerritMerged openstack/releases: oslotest 1.5.2  https://review.openstack.org/20217718:52
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: Prototype script to release from the new YAML files  https://review.openstack.org/20224019:07
dhellmannlifeless: I'm thinking about how to update the release tools as a python library and cli, and one of the things I want to handle properly is the local repository thing you need. Do you have a bunch of repositories checked out in a flat directory ( .../nova, .../release-tools) or do you have them under the namespaces like in gerrit ( .../openstack/nova, .../openstack-infra/release-tools)?19:15
lifelessdhellmann: namespaced19:16
lifelessdhellmann: as gertty produces in fact, or the adhoc script involved by querying gerrit19:16
dhellmannlifeless: ok, cool, so if there was a configuration option for the root of that dir, that would work for you19:16
dhellmannthat's how I do it, too, with the script in oslo-incubator19:17
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: Move release_notes.py into releasetools package  https://review.openstack.org/20225720:06
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: Move release_notes.py into releasetools package  https://review.openstack.org/20225720:13
*** dims_ has quit IRC21:07
*** bnemec has quit IRC21:43
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: Move release_notes.py into releasetools package  https://review.openstack.org/20225722:42
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move list-repos into the releasetools project  https://review.openstack.org/20232022:42
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move commands into their own package  https://review.openstack.org/20232122:42
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move get_project_for_repo.py into the releasetools package  https://review.openstack.org/20232222:42
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move sanity-check-version into releasetools package  https://review.openstack.org/20232322:42
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move rename_milestone.py to milestone-rename  https://review.openstack.org/20232422:42
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move ensure_milestone.py to milestone-ensure  https://review.openstack.org/20232522:42
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move close_milestone.py to milestone-close  https://review.openstack.org/20232622:42
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move create_milestones.py to milestones-create  https://review.openstack.org/20232722:42
dhellmannttx: that series of patches is refactoring work to prepare for rewriting the release script in python ^^22:42
*** dims_ has joined #openstack-relmgr-office22:51
*** sigmavirus24 is now known as sigmavirus24_awa22:51
*** mestery_ has joined #openstack-relmgr-office23:00
*** mestery has quit IRC23:03

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