/srv/irclogs.ubuntu.com/2016/06/08/#ubuntu-meeting.txt

=== JanC is now known as Guest74845
=== JanC_ is now known as JanC
=== sarnold is now known as sarnold_
=== Guest47242 is now known as med_
thedaco/16:59
gnuoyo/17:00
jamespageo/17:00
iceyop/17:00
cargonzao/17:00
gnuoytinwood, beisner, coreycb, ddellav today?17:00
gnuoy#startmeeting openstack-charms-meeting17:00
meetingologyMeeting started Wed Jun  8 17:00:48 2016 UTC.  The chair is gnuoy. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
meetingologyAvailable commands: action commands idea info link nick17:00
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | openstack-charms-meeting | Current topic:
beisnero/17:00
gnuoy#topic Review ACTION points from previous meeting17:00
ddellavo/17:00
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | openstack-charms-meeting | Current topic: Review ACTION points from previous meeting
gnuoy#subtopic gnuoy Talk to stub about moving his leadership layer into core17:01
tinwoodo/17:01
gnuoyThis is less relevant as I went a different path17:01
gnuoyI ended up gating things like db_sync on leadership down in the layer itself rather than in the top handler17:01
gnuoyI'll close that action17:02
gnuoy#subtopic gnuoy review 16.07 deliverables17:02
gnuoyI'll defer this again until we're closer to the date17:02
gnuoy#subtopic jamespage update on relicensing of charms17:02
gnuoyHe is going to contact people outside of Canonical who have contributed to the charms and ask if they are happy if the licensing of the charm moves from GPL v3 to Apache-2.0. This is so that our charms comply with the licensing policy for OpenStack big-tent projects17:02
gnuoy#link http://governance.openstack.org/reference/licensing.html17:02
jamespageok17:02
jamespageI've sent email to openstack-dev with intent; and emailed contributors outside of canonical directly to ask them to respond on the ML thread17:02
gnuoyexcellent, thank you17:03
gnuoy#topic Moving communication Upstream17:03
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | openstack-charms-meeting | Current topic: Moving communication Upstream
gnuoyWe're currently pushing communication to upstream channels. So, we'll be creating a new openstack-charms IRC channel on freenode and moving email discussions about charm operation and charm development to the OpenStack mailing lists.17:03
gnuoyIn addition we'll be pushing to update our documentation, both in the charms and various web pages.17:03
jamespagewe should probably move this meeting to an openstack-meeting channel as well?17:04
gnuoyEmails the OpenStack mailing lists should have [charm] at the start of their subject line17:04
gnuoyjamespage, +117:04
jamespagegnuoy, are you ok to take an action to make that happen?17:04
beisner#link http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev17:04
gnuoy#action gnuoy move meeting to openstack-meeting channel17:04
meetingologyACTION: gnuoy move meeting to openstack-meeting channel17:04
tinwoodWe tend to have most conversations on irc.  When do they/should they move to he ML?17:04
beisnerjamespage, gnuoy - meeting time slots on the 2 (or 3) openstack-meeting channels is pretty tight.   some projects use their own channel, and that can be an ok option i think.17:05
gnuoytinwood, I don't think we should move conversations to a mailing list17:05
jamespagethat's a good question - I think when its something design oriented or significant17:05
jamespageML17:05
jamespageotherwise general chat still in irc imhp17:05
gnuoy+117:05
tinwoodsounds good17:05
gnuoybeisner, ok, thanks for the heads up17:05
beisner+1 irc for day to day convos17:05
jamespageI proposed a rename of the openvswitch-odl charm - that's probably a good example17:05
beisnerindeed17:06
* gnuoy needs to fiddle with email filters17:06
tinwoodSo things that have knock on effects, etc.17:06
gnuoy#topic State of Development for next Charm Release17:06
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | openstack-charms-meeting | Current topic: State of Development for next Charm Release
gnuoyMost of the HA code in the OpenStack layers has now landed, so OpenstackCharms built on top of the Openstack Layers should be able to easily enable service HA. Work continues on DNS HA, Barbican and workload status management in the OpenStack layers. anyone, want to add anything?17:07
jamespagehow are we with CI progress beisner?17:07
beisnerwe're now adding a repo-info on the fly just ahead of push and publish to the charmstore17:08
beisnerthat will allow users / triagers to determine exactly where a cs: revno came from17:08
jamespage\o/17:08
beisnerthose files should never live in the charm source repos - only ever in a built/published artifact17:09
beisnerexample:  https://jujucharms.com/tempest/17:09
gnuoythanks beisner17:09
beisnernext up is injecting the build step into the existing CI, which I plan to have tactically in place this week.17:09
gnuoytip top17:09
thedacnice17:09
beisnerwe'll have some things to adjust i'm sure, but the basic commit -> build -> test -> publish flow should be good17:10
gnuoy#topic Release Bugs17:10
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | openstack-charms-meeting | Current topic: Release Bugs
gnuoy#link https://goo.gl/HJjORI17:10
gnuoyI haven't gone through them in the last week but will be looking through again tomorrow. If anyone has anytime to look as well that would be great.17:10
gnuoyWe're one up on last week I think, so not exactly an avalanche, although I think jamespage has done some work17:10
gnuoy#topic Open Discussion17:11
gnuoyAnyone got anything OpenStack charm related to get off their chests?17:11
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | openstack-charms-meeting | Current topic: Open Discussion
gnuoyanyone got anything on their mind?17:11
beisnersrc dirs are still on my mind17:11
gnuoyin a good way?17:12
beisner;-)17:12
tinwoodLike or dislike17:12
beisneri may have waffled on ya17:12
beisnerlet's discuss in more detail in day 2 day though.  proceeding to support both methods (vanilla layers, and the proposed src charm model)17:12
thedacha!17:12
gnuoykk17:13
thedacFWIW I lean toward no src dir17:13
tinwoodsplitter17:13
beisneri'd like to see us list the distinct benefits of doing it really17:13
* tinwood is sorry17:13
beisnerother than it feels/looks better, naturally :)17:14
gnuoyyes, it does17:14
tinwoodI'll add to the design doc on CI some points.17:14
gnuoyfeels/looks better, I mean17:14
beisnerfrom a devex perspective, having another method could be confusing17:15
beisnertake the cephs17:15
beisnerceph-osd and ceph-mon are to be vanilla layers.  buildable as a charm and consumable as a layer.17:15
beisnerbut the ceph layer would be  src charm, with a diff dir structure17:15
beisnerie ceph layer not intended to be reconsumed as a layer17:15
tinwoodShould the ceph-osd/ceph-mon be layers AND charms?17:16
beisnerthat's a good question.  the *can* be.   should they?17:16
tinwoodi.e. another 'thing' that trivally consumes the ceph-osd layer to be the charm.17:16
beisnerso charm-layer-ceph-osd with the guts, and a thin wrapper in charm-ceph-osd?17:17
tinwoodpossibly, although even that feels like a hack.17:17
beisnerwith the latter being a src charm17:17
beisneri think it's one or the other isn't it?17:18
tinwoodyes17:18
gnuoyI don't feel that strongly tbh. I like the src dir because it means that files which are only used to build the charm do not pollute the built charm but *shrug*17:19
thedacMy arguments against src dir are 1) We are artificially introducing the concept of "top layer"  2) Theoretical future need to consume "top layer" as a middle layer (cephs good example) 3) The developers of reactive and the first reactive charms don't use a src dir17:20
beisneri agree with that aesthetic benefit entirely17:20
thedacBut I am certainly open to debate17:20
gnuoyI think point 2 could be argued both ways tbh17:20
thedacI am just publicly committing to my argument :)17:21
gnuoyIf we don't want a top layer to be consuable the src dir is a good way to distinguish it.17:21
gnuoyI find the argument that the src charm is a layer a bit force tbh17:21
beisnerit feels a bit like building a thing but then saying:  you can't extend or re-use it for some other currently unimagined purpose.17:21
thedacAnd my point is how can we know for certain now that some point in the future we will not want/have to consume a "top" layer again the cephs are good examples17:22
tinwoodI'm not overly attached either way.17:22
jamespageI don't think using the src directory now precludes us from moving a charm to be a layer later...17:23
beisnertrue, git mv ftw17:23
jamespageat least that way we are making a explicit decision that a charm is now consumable as a layer...17:23
thedacThat is the strongest point for src dir. That we are explicitly stating it is NOT supported as a layer17:24
gnuoyjamespage, please review the etiquette guidelines (https://wiki.ubuntu.com/ServerTeam/OpenStackCharmsMeeting)17:24
beisnerlolz17:24
jamespage..17:25
jamespageoops lol17:25
beisnerroflcopters17:25
thedacheh17:25
gnuoyOk, I think we should plough on with the src dir but retain the right to change our minds17:25
* tinwood lol17:25
jamespage+117:25
* thedac falls in line17:26
jamespagecan we have a official vote on that?17:26
tinwoodhow do we vote?17:26
gnuoywe can but I don't know the meeting bot commans17:26
gnuoy* commands17:26
jamespage#vote17:26
jamespage#vote <subject>17:26
coreycbo/17:26
jamespagehttps://wiki.ubuntu.com/meetingology17:26
gnuoy#vote Having a src dir in top layer charms17:26
meetingologyPlease vote on: Having a src dir in top layer charms17:26
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)17:26
jamespage+117:27
meetingology+1 received from jamespage17:27
icey+017:27
meetingology+0 received from icey17:27
thedac+017:27
meetingology+0 received from thedac17:27
gnuoy#voters all17:27
meetingologyEveryone can now vote17:27
tinwood+117:27
meetingology+1 received from tinwood17:27
coreycb+017:27
meetingology+0 received from coreycb17:27
beisneryes, happy to pave the ci for both to 'just work' -- i only hold back for the future questions: "you did what?"17:27
gnuoy+117:27
meetingology+1 received from gnuoy17:27
beisner+017:27
meetingology+0 received from beisner17:27
gnuoy#votesrequired 317:28
meetingologyvotes now need 3 to be passed17:28
gnuoyargh, I think we're done17:28
gnuoy#endvote17:28
meetingologyVoting ended on: Having a src dir in top layer charms17:28
meetingologyVotes for:3 Votes against:0 Abstentions:417:28
meetingologyMotion carried17:28
jamespage\o/17:28
tinwood\o/17:28
thedac:)17:28
gnuoy#topic Announce next meeting date, time and chair17:28
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | openstack-charms-meeting | Current topic: Announce next meeting date, time and chair
gnuoyjamespage, you#re down for next week, can you managed that, I know its late in the UK?17:28
gnuoyif not you can always swap I guess17:29
gnuoyDate 2016-06-15, same time, same place17:29
beisnercomedians here today, jeez!17:29
jamespageI can17:29
gnuoy#endmeeting17:29
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Jun  8 17:29:24 2016 UTC.17:29
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-06-08-17.00.moin.txt17:29
beisnerthx gnuoy & thx all17:29
coreycbthanks gnuoy17:29
iceythanks!17:29
thedacthanks gnuoy17:29
gnuoynp17:29
tinwoodthanks gnuoy17:30
jamespagethanks gnuoy17:30
jamespagettfn17:30
=== lifeless_ is now known as lifeless

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