Tuesday, 2018-09-18

openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324600:15
openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324600:18
*** aagate has quit IRC00:19
openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324600:21
jayahnmark-burnett: "Every Thursday, alternating between 10 AM EST, vs 4 PM EST", which one is for this week? 10AM? 4PM?00:26
openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324601:25
*** felipemonteiro has quit IRC01:38
*** felipemonteiro has joined #airshipit01:54
*** felipemonteiro has quit IRC02:10
openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324602:37
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: [wip] Jenkins pipeline for airship-seaworthy  https://review.openstack.org/59219002:42
*** roman_g has quit IRC02:46
*** felipemonteiro has joined #airshipit02:58
openstackgerritMerged openstack/airship-drydock master: Back-off pyghmi upgrade  https://review.openstack.org/60318603:08
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: [wip] Jenkins pipeline for airship-seaworthy  https://review.openstack.org/59219003:11
*** felipemonteiro has quit IRC03:23
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: [wip] Testing drydock pyghmi fix  https://review.openstack.org/60327403:29
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: [wip] Jenkins pipeline for airship-seaworthy  https://review.openstack.org/59219003:44
*** felipemonteiro has joined #airshipit03:46
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: Jenkins pipeline for airship-seaworthy  https://review.openstack.org/59219003:47
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: Jenkins pipeline for airship-seaworthy  https://review.openstack.org/59219003:48
*** felipemonteiro has quit IRC03:52
*** felipemonteiro has joined #airshipit03:56
*** felipemonteiro has quit IRC04:00
openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324604:10
*** cfriesen has quit IRC04:27
openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324604:32
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: [wip] Testing drydock pyghmi fix  https://review.openstack.org/60327404:59
openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324605:02
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: [wip] Testing drydock pyghmi fix  https://review.openstack.org/60327405:07
openstackgerritCraig Anderson proposed openstack/airship-divingbell master: fix divingbell gate scripts  https://review.openstack.org/60324605:46
ethfciroman_f: ubuntu@n0:~$ nslookup att.com05:59
ethfciServer:192.168.77.105:59
ethfciAddress:192.168.77.1#5305:59
ethfciNon-authoritative answer:05:59
ethfciName:att.com05:59
ethfciAddress: 144.160.36.4205:59
ethfciName:att.com05:59
ethfciAddress: 144.160.155.4305:59
ethfciubuntu@n0:~$ nslookup google.com05:59
ethfciServer:192.168.77.105:59
ethfciAddress:192.168.77.1#5305:59
ethfciNon-authoritative answer:05:59
ethfciName:google.com05:59
ethfciAddress: 172.217.21.17405:59
ethfciubuntu@n0:~$ nslookup att.com05:59
ethfciServer:192.168.77.105:59
ethfciAddress:192.168.77.1#5306:00
ethfciNon-authoritative answer:06:00
ethfciName:att.com06:00
ethfciAddress: 144.160.36.4206:00
ethfciName:att.com06:00
ethfciAddress: 144.160.155.4306:00
ethfciubuntu@n0:~$ nslookup google.com06:00
ethfciServer:192.168.77.106:00
ethfciAddress:192.168.77.1#5306:00
ethfciNon-authoritative answer:06:00
ethfciName:google.com06:00
ethfciAddress: 172.217.21.17406:00
ethfci the setup is libvirt based ith has dnsmasq06:00
ethfciroman_g it seems to me i should stop using libvirt-dnsmasq, thanks for the hint06:15
ethfciubuntu@n0:~$ dig +time=2 +tries=1 att.com @153.88.112.20006:15
ethfci; <<>> DiG 9.10.3-P4-Ubuntu <<>> +time=2 +tries=1 att.com @153.88.112.20006:15
ethfci;; global options: +cmd06:15
ethfci;; Got answer:06:15
ethfci;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 246106:15
ethfci;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 106:15
ethfci;; OPT PSEUDOSECTION:06:15
ethfci; EDNS: version: 0, flags:; udp: 400006:15
ethfci;; QUESTION SECTION:06:15
ethfci;att.com.INA06:15
ethfci;; ANSWER SECTION:06:15
ethfciatt.com.300INA144.160.36.4206:16
ethfciatt.com.300INA144.160.155.4306:16
ethfci;; Query time: 182 msec06:16
ethfci;; SERVER: 153.88.112.200#53(153.88.112.200)06:16
ethfci;; WHEN: Tue Sep 18 08:09:50 CEST 201806:16
ethfci;; MSG SIZE  rcvd: 6806:16
*** georgk has joined #airshipit07:53
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-treasuremap master: [WIP] Delivery of default seccomp Profile on each Host on site deployment  https://review.openstack.org/60253208:04
*** roman_g has joined #airshipit10:37
*** mardim has quit IRC10:58
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-drydock master: Update node-labels through Kubernetes Provisioner  https://review.openstack.org/59360911:00
*** mardim has joined #airshipit11:03
roman_gmark-burnett: Hi Mark. Is Airship meeting still on Tuesdays?11:11
roman_gHaven't found logs for lats 2 meetings in September https://etherpad.openstack.org/p/airship-team-meeting-agenda11:12
roman_g*last11:12
openstackgerritSmruti Soumitra Khuntia proposed openstack/airship-drydock master: Update node-labels through Kubernetes Provisioner  https://review.openstack.org/59360913:23
mark-burnett@roman_g meetings are still on Tuesdays.  I'm not sure where the 9/11 meeting notes are, but there was no 9/18 meeting, because of the PTG.13:24
mark-burnettWoops, off by a week sorry - there was no 9/11 meeting because of the PTG13:27
*** sthussey has joined #airshipit13:36
*** aaronsheffield has joined #airshipit13:38
evrardjpmark-burnett: :)13:45
mark-burnett:)13:46
*** sgrasley has joined #airshipit13:47
roman_gmark-burnett: thanks13:48
roman_ggood morning13:48
mark-burnettmorning, i updated the list too for more clarity13:48
openstackgerritRoman Gorshunov proposed openstack/airship-treasuremap master: New option --out-file, fixes for retries logic  https://review.openstack.org/60339513:56
sthusseyhere14:00
mark-burnett#startmeeting airship14:00
openstackMeeting started Tue Sep 18 14:00:21 2018 UTC and is due to finish in 60 minutes.  The chair is mark-burnett. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
portdirecto/14:00
*** openstack changes topic to " (Meeting topic: airship)"14:00
openstackThe meeting name has been set to 'airship'14:00
mark-burnettHi all, thanks for coming14:00
aaronsheffieldo/14:00
roman_go/14:00
mark-burnettHere's our agenda for the meeting: https://etherpad.openstack.org/p/airship-meeting-2018-09-1814:00
mattmceueno/14:00
mark-burnettPlease feel free to add items14:01
mark-burnett#topic Meeting reschedule14:02
*** openstack changes topic to "Meeting reschedule (Meeting topic: airship)"14:02
mark-burnettWe've talked about this for quite a long time, and it seems that there's no traction for moving it14:02
mark-burnettEveryone who voted in the doodle selected the current time14:03
mark-burnettWe didn't really get much participation from people who don't already attend14:03
mark-burnettI think we should simply table this until it comes up again organically.  Any other thoughts?14:03
seaneagano/14:03
roman_gI'm OK with this time and frequency.14:03
mattmceuenSounds reasonable to me14:04
roman_gYes, table it.14:04
sthusseyI believe the genesis for the request was the edge cloud14:04
sthusseySo maybe in the meantime, if there is a contact there the doodle could be provided such that those interested in attending both could vote14:04
mark-burnettYeah, that was a big motivator14:05
mattmceuenMaybe let's connect with Chris H on this14:05
mark-burnett@hogepodge ^14:05
mattmceuenLet him make sure it gets in front of "the right people"14:06
mattmceuenOh look there he is ;-)14:06
openstackgerritAndrey Volkov proposed openstack/airship-shipyard master: Ensure Drydock pod logs are fetched in case of any exceptions  https://review.openstack.org/60339814:06
mark-burnettLet's leave it at that for now then14:06
mark-burnett#action mark-burnett work with hogepodge reach out to others who didn't participate in discussion about rescheduling14:07
mark-burnett#topic PTG14:07
*** openstack changes topic to "PTG (Meeting topic: airship)"14:07
mark-burnettWe had pretty great attendance in our room at the PTG!14:07
mark-burnettThanks everyone for contributing14:07
mark-burnettI listed some of the interested attendees in the etherpad, but there were also some really great questions and thoughts from other folks too14:08
roman_gHow many people?14:08
mark-burnettWell, Monday morning, there was not enough room at the tables really.  I guess that was roughly 20 people?14:08
mark-burnettI should have counted -- 2 or 3 people were literally sitting on the floor until we got more chairs14:08
mattmceuenHere's the etherpad, where some notes were captured if anyone wants to catch up:  https://etherpad.openstack.org/p/AirshipPTG414:09
mark-burnettThanks mattmceuen14:09
mark-burnettI'll write up a digest email and send it to the list this week14:09
mark-burnett#action mark-burnett write digest of PTG notes for the mailing list14:09
hogepodgehi14:09
mark-burnettHey Chris14:10
mark-burnettDoes anyone have any other thoughts about how the PTG went?14:11
portdirectI thoughr it was pretty good14:11
* roman_g wants to participate.14:11
portdirectthere was a lot of interest, esp in a 'stepped' airship14:11
hogepodgeI don't know of anyone who wanted a different time. I'll check with ildiko but aside from waking up early here ;-) it should be fine14:12
portdirectas many orgs found the full stack a bit much, eg they have a bm/k8s provisioner14:12
portdirector are simply looking to get there toes wet14:12
roman_gportdirect, you mean that many of them want to use only specific parts of airship-*?14:12
sthusseyseems like Armada would be a good fit for them then14:12
portdirecttime will tell how much interest turns into contributions, but theres def great potential14:13
mattmceuenAgree, that was the biggest "surprise" use case for me - there were other use cases / enhancements we knew would be useful that other folks were in large agreement in too, and it was really good fleshing those out a bit with potential users/contributors14:13
portdirectsthussey: armada, into dechand, and also shipyard14:13
portdirectand at that stage...14:13
portdirectwhy not eat the whole cake ;)14:13
mark-burnettIndeed, there are teams that dont' control hardware provisioning who want to leverage as much of the declarative approach as they can14:14
mark-burnettfor example14:14
portdirectthere was also a strong desire to make things pluggable, eg kubeadm instead of (or driven by) promenade14:14
portdirectand ironic as a back end for maas14:15
sthusseyDrydock is pluggable14:15
sthusseyIf someone wants Ironic, the design supports them adding it14:15
portdirectyeah 0 though someone needs to step up and write the plug ;)14:15
mattmceuenYup, we discussed that and there was a lot of support for it14:15
sthusseyIt seems kubeadm would mostly be a alternative to promenade14:15
portdirectthere was also some discussion later in the week on the use of yaml for deckhand14:16
portdirectwhere a few people expressed an interest in json responses14:16
portdirectthough fmonetro has a better understanding of the discussion there.14:16
sthusseySounds like there is a lot of room for some speculative designs14:17
sthusseyWill be great to see specs written up by those interested in these enhancements14:17
portdirect++14:17
jayahno/14:17
mark-burnettHi jay :)14:17
jayahnhi14:18
portdirecton the subject of `stepped` airship - I think mattmceuen 's work on airskiff has great potential there.14:18
jamesgu__++14:18
portdirectas it's already 90% of what people were expressing an interest in.14:18
portdirectin addtion to the full stack.14:19
sthusseyThere you go14:19
jamesgu__airskiff is a step up itself to just using the Armada14:20
mattmceuenThanks portdirect - I think that's a good POC of the concept, and I think some additional things would need to be done to make the concept work well in a real life deployment14:20
mattmceuenE.g. there was discussion around leveraging drydock to potentially manage machines that were brought in a "bring your own OS" type scenario14:20
mattmceuenBut we can evolve to those14:21
jamesgu__or possible to bring in promenade in the bring your own hardware?14:21
mark-burnettI think airskiff is basically just running helm install on the airship charts on an existing kube cluster14:22
sthusseyI think most of this needs to be put together in a cohesive spec14:23
mark-burnettI think if we're going to implement a tiered approach, the components will need to be armada-managed14:23
mattmceuenYup, that's it.  In an eventual, target-state BYO{x} it would be nice to use an armada-based deployment14:23
sthusseyAd hoc IRC discussion probably omits too many details to be valuable14:24
mark-burnettYeah, a spec would be useful here so that intent is really clear14:24
mark-burnettWhat is in bounds and what is out14:24
mattmceuenSounds like good discussion for Rodolfo's weekly design call as well14:24
mattmceuenTo figure out what should go into the spec14:25
jayahnspeaking of design call, why it is so~~ difficult to find out this week's design meeting time. I found etherpad, I found design meeting is switching time, but not the exact information on this week's time. it should be really easy information to find.14:25
mark-burnettGood point Jay, let me add it to the main etherpad for reference: https://etherpad.openstack.org/p/airship-team-meeting-agenda14:25
mark-burnettI'll put that in there today14:25
mark-burnett#action mark-burnett make sure the design call details are in this etherpad: https://etherpad.openstack.org/p/airship-team-meeting-agenda14:25
mark-burnettOn another note, there was some discussion in the infra team about how to facilitate screen sharing/phone calls while still achieving good accessibility14:26
jayahnI don't want to move a topic away.. but, it should be really easy information to find like other openstack-meeting information.14:26
mark-burnettAs mattmceuen said, we need to make sure that the important parts of design conversations are captured in specs14:27
mattmceuenAgree jayahn, any suggestions?14:27
jamesgu__before we move on to next topic, with the discussion of a spec, sounds like the plan is to move Airskiff to Openstack proper?14:27
mattmceuenon where we could put the info14:27
mattmceuenLet me clarify14:27
mark-burnett@jamesgu__ I think we need to figure out a plan before we do that14:27
mark-burnettIt's not clear there needs to be a new component here14:28
mattmceuenre: airskiff - because it got some good attention at the PTG (#flattering)14:28
mattmceuenAirskiff was intented first and foremost to be a dev environment14:28
mattmceuenWe discussed at the PTG using "airskiff approach" for two additional things14:28
mattmceuengating14:28
mattmceuenbyo{X}14:28
mattmceuenI think those are great use cases, and I don't want to shoehorn anything so important into my github repo :)14:29
mattmceuenSo to your question14:29
roman_gjamesgu__: as usual, all OpenStack projects meetings are described here, including Airship: http://eavesdrop.openstack.org/#Airship_Team_Meeting . Please, check it out.14:29
mattmceuenI will be working w/ Drew this week to adjust his PS for additional gates per our discussion @ the PTG14:29
mattmceuenI want to use the airskiff approach (which is really the openstack-helm approach that I borrowed) for some very lightweight gates14:29
mattmceuenThat will start out as nonvoting14:29
mattmceuenAnd use the treasuremap manifests as much as possible14:30
mark-burnettThis probably belongs in the design call, but it seems to me that we could make a small change to armada and simply use that directly14:30
sthusseyI believe there is a meeting topic on testing methods14:30
mattmceuenSo that work will move into treasuremap proper as a new home, but if it makes sense I'll still keep airskiff around as a separate dev playground14:30
mark-burnettLet's move on to new business14:31
mark-burnett#topic Policy for idle patchsets14:31
*** openstack changes topic to "Policy for idle patchsets (Meeting topic: airship)"14:31
mark-burnettI don't have the links off hand, but there are a couple of older changes that are unlikely to merge and should probably be abandoned14:32
mark-burnettWe probably need a simple way of determining whether/when to abandon submitted changes14:32
mark-burnettSuggestions?14:33
sthusseyI think 60 days of inactivity should be abandoned14:33
roman_gBot, adding comments to the change if it's stale for 4 weeks, and abandoning if no replies after 8 weeks.14:33
mark-burnettThose sound really similar and fair to me14:34
roman_gBut does it hurt to have patch sets which are abandoned?14:35
mark-burnettShould we try a manual version of what roman suggests and see how it goes?  Certainly people can recreate abandoned changes later if that is useful.14:35
roman_gI mean, if author does not care to ask for reviews, then why would we care?14:35
roman_ggerrit will not break14:36
evrardjpmark-burnett: 365 days14:36
mattmceuenYou can also un-abandon PS14:36
evrardjpyup14:36
mark-burnett@evrardjp why do you propose that timeline specifically?14:36
evrardjphabit :)14:37
mattmceuenlol14:37
mark-burnettha, gotcha14:37
evrardjpeasy to check14:37
sthusseyI'd prefer to be a bit more agressive14:37
sthusseyAs the cores, though it is not apparent, do try to keep the open PS list down14:37
roman_gGerrit auto-abandon changes which are stale for certain period of time: https://gerrit-review.googlesource.com/Documentation/user-change-cleanup.html14:37
evrardjpby default it's to 014:38
evrardjpiirc14:38
sthusseyThat looks to be an optional configuration.14:38
sthusseyMaybe this is something that Airship projects could tune in openstack-infra14:38
evrardjpit's probably something we can ask infra14:38
evrardjphahah14:38
evrardjpyeah14:38
evrardjpmaybe14:38
evrardjpnot sure if it's global or not14:38
mark-burnettyeah, not clear14:38
evrardjpif it's per gerrit instance it will not happen14:39
evrardjpand it kinda looks like it: etc/gerrit.config  :)14:39
mark-burnettWell, let's vote on a manual policy and see what happens about automation later14:39
evrardjpI guess it's worth asking on infra to document the manual policy decision14:39
evrardjpshould someone ask again14:39
mark-burnett#startvote How long should we leave changes inactive before abandoning?  Options: 1M, 2M, 1Y, Never Abandon.14:40
openstackBegin voting on: How long should we leave changes inactive before abandoning? Valid vote options are Options, 1M, 2M, 1Y, Never, Abandon, .14:40
openstackVote using '#vote OPTION'. Only your last vote counts.14:40
roman_gActually, documentation says that patch sets should auto-abandon in 2 weeks of no-touch https://docs.openstack.org/infra/system-config/gerrit.html#auto-review-expiry14:40
mattmceuenwow, two weeks14:41
mark-burnettIs that just one specific project?14:41
roman_g#vote 2M14:41
mattmceuenthat's harsh for contributors that may not be e.g. full-time on the project, in my opinion14:41
evrardjpnot sure if it still applies.14:41
mark-burnett#vote 2M14:41
portdirect#vote 2M14:41
mattmceuen#vote 2M14:41
aaronsheffield#vote 1M14:41
jayahn#vote 2M14:42
jamesgu__#vote 2M14:42
evrardjpI guess the winner is clear :)14:42
mark-burnettIt seems, but let's give it another minute in case someone has a strong objection14:42
sthussey#vote 2M14:43
mark-burnettOk, ending in a efw seconds14:43
mark-burnett#endvote14:44
openstackVoted on "How long should we leave changes inactive before abandoning?" Results are14:44
openstack2M (7): mark-burnett, portdirect, jayahn, roman_g, mattmceuen, jamesgu__, sthussey14:44
openstack1M (1): aaronsheffield14:44
openstackgerritDrew Walters proposed openstack/airship-shipyard master: wip: plugins: Add Armada subdag/operator for helm tests  https://review.openstack.org/60323614:44
mark-burnettOk, so let's start enforcing a manual policy of giving change authors notice of the policy after ~1M and then abandoning old changes at 2M14:44
mark-burnett#agreed We will abandon changes that have been idle for 2 months, and give authors notice of this policy at approximately 1 month of idle time.14:45
mark-burnett#topic Testing Policy Reminder14:45
*** openstack changes topic to "Testing Policy Reminder (Meeting topic: airship)"14:45
mark-burnettQuick note on testing changes - in particular for promenade and drydock, which touch a lot of pieces14:46
mark-burnettPlease be sure to run the prom resiliency gate for promenade changes.  We have not been able to get this going in Zuul yet (or in AT&T-provided 3rd party gating), but it's pretty easy to run locally (if you have about 12G of ram).14:46
mark-burnettIt takes about 30 minutes to run on my laptop, for reference14:47
mark-burnettFor drydock, the situation is a bit trickier, but there is a similar test (the multi-node gate in airship-in-a-bottle).14:47
mark-burnettFeel free to reach out for help with these, or even better start trying to get them working in zuul :D14:47
mark-burnett#topic Collaboration Opportunities14:48
*** openstack changes topic to "Collaboration Opportunities (Meeting topic: airship)"14:48
mark-burnettI was super excited to talk to Jay and James at the PTG about working on airship :)14:49
mark-burnettI don't have anything to add beyond the brief snippets in the etherpad14:49
jayahnyeap. just want to do quick intro on this week's design call, and figure from there14:49
mark-burnettAwesome, I'll make sure those details are added14:49
mark-burnettto the etherpad, as above14:49
jayahnthanks14:50
mark-burnett#topic Development Update14:50
*** openstack changes topic to "Development Update (Meeting topic: airship)"14:50
mark-burnettJust a reminder to add notable development activities to https://etherpad.openstack.org/p/airship-dev-update-2018-10-05 so that I can write something up for the list14:51
mark-burnettI'm targeting 10/5 this go around14:51
roman_gwould versions.yaml updater fit there?14:51
mark-burnettYes!14:51
mark-burnettGood though :)14:51
mark-burnettt14:51
mattmceuen++14:51
mark-burnett#topic Reviews14:52
*** openstack changes topic to "Reviews (Meeting topic: airship)"14:52
mark-burnettI don't really have anything to say on this one14:52
mark-burnettOthers may have?14:52
* mattmceuen is still clueless after long weekend14:53
mark-burnettOk, let's punt.  If it's an issue we can add it for next week.14:54
mark-burnett#topic reviewbot noise14:54
*** openstack changes topic to "reviewbot noise (Meeting topic: airship)"14:54
mark-burnettI think @roman_g raised the idea that every `git review` leading to an irc message is a bit spammy14:54
roman_gYes, I have raised it.14:55
roman_gI (roman_g) look for questions from community members, and ask for reviews, and ask for help from developers. I don't look at openstackgerrit bot notifications - they only show to me that someone is working.14:55
mark-burnettI personally agree with the opinion of keeping a single irc channel for now, so I'm not too excited about splitting even for a build-notification channel14:55
mark-burnettI don't really use the notifications, as I just look through the gerrit list directly14:55
roman_gDo I go and checkout everyone's review once I see notification from the bot? - No.14:56
roman_gFor me it's useless. So far.14:56
mark-burnettI've seen this pattern be useful to some members on smaller teams, but I agree with you overall roman_g .14:56
mark-burnettI would start a vote, but I think most people have gone14:57
mark-burnettI think an hour is too long for us :/14:57
b-strIf there were a way to do a digest, that might be nice14:57
roman_gMay be notification on merges would be better.14:57
mark-burnett@b-str interesting idea14:57
mark-burnett@roman_g maybe so, yes, but that's not a call to action for devs14:58
mark-burnettusually14:58
mark-burnettLet's add it to next week for a vote14:58
mark-burnettI don't think we should vote with 2 minutes left and waning attendence14:58
mark-burnett#topic Marketing Deadlines14:58
*** openstack changes topic to "Marketing Deadlines (Meeting topic: airship)"14:58
mark-burnettLooks like October 1 is the deadline for single page marketing doc and updated website content14:59
mark-burnettI think there's a google doc for the 1 page, but I don't have it handy14:59
hogepodgeyes, our design team needs lead time to produce everything for Berlin14:59
mark-burnettRight14:59
mark-burnettWhat is the best way to give feedback for the website?15:00
mark-burnettWe can link the google doc for the 1-pager15:00
hogepodgeI've been flowing in a lot of content for the one pager, and will have that and some preliminary website content ready for our meeting on Thursday15:00
mark-burnettok cool15:00
mark-burnettThanks hogepodge15:00
mark-burnettalright, let's wrap up15:00
mark-burnett#topic roundtable15:00
*** openstack changes topic to "roundtable (Meeting topic: airship)"15:00
mark-burnettAny last minute thoughts?15:00
portdirectdid we have time to discuss -2 reviews?15:01
hogepodgeYeah, we'll need major feedback from you starting Thursday, due by the end of the month (plus revised diagram drafts)15:01
mark-burnettWe already hit that topic @portdirect15:01
portdirectmust have missed it - damn i created it as well!15:01
portdirectlol15:01
mark-burnett:)15:01
mark-burnettWe can add it for next week if you like15:01
portdirectyes please15:02
portdirectthx15:02
mark-burnettok, let's close15:02
mark-burnett#endmeeting15:02
*** openstack changes topic to "airshipit.org || General Review Dashboard: https://review.openstack.org/#/q/project:%255Eopenstack/airship.*+status:open,n,z"15:02
openstackMeeting ended Tue Sep 18 15:02:18 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2018/airship.2018-09-18-14.00.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2018/airship.2018-09-18-14.00.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2018/airship.2018-09-18-14.00.log.html15:02
roman_gThanks everyone.15:02
openstackgerritMerged openstack/airship-in-a-bottle master: Fixed permission issue to run as non-root  https://review.openstack.org/60278515:09
hogepodgereminder, forum session submissions are open now15:12
hogepodgehttps://wiki.openstack.org/wiki/Forum15:13
*** felipemonteiro has joined #airshipit15:24
*** jamesgu has joined #airshipit15:38
*** felipemonteiro has quit IRC15:39
*** jamesgu__ has quit IRC15:41
openstackgerritAaron Sheffield proposed openstack/airship-promenade master: [WIP] Enabled AppArmor for K8s Proxy  https://review.openstack.org/60244416:16
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: Change image update logic to latest in quay.io  https://review.openstack.org/60241816:29
openstackgerritRoman Gorshunov proposed openstack/airship-treasuremap master: New option --out-file, fixes for retries logic  https://review.openstack.org/60339516:36
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: Jenkins pipeline for airship-seaworthy  https://review.openstack.org/59219019:14
openstackgerritMatt McEuen proposed openstack/airship-specs master: Spec: Pegleg encryption and decryption  https://review.openstack.org/60347319:17
openstackgerritSangeet Gupta proposed openstack/airship-promenade master: APISERVER for webhook  https://review.openstack.org/59526319:50
openstackgerritSangeet Gupta proposed openstack/airship-promenade master: APISERVER for webhook  https://review.openstack.org/59526320:04
openstackgerritMerged openstack/airship-deckhand master: Adding api for revisions deep diffing  https://review.openstack.org/59535920:16
*** munimeha1 has joined #airshipit20:31
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: Jenkins pipeline for airship-seaworthy  https://review.openstack.org/59219021:21
*** aaronsheffield has quit IRC21:29
openstackgerritAnthony Bellino proposed openstack/airship-armada master: Network Policy  https://review.openstack.org/59526621:34
*** georgk has quit IRC21:40
openstackgerritPRATEEK REDDY DODDA proposed openstack/airship-deckhand master: First push attempt  https://review.openstack.org/60350221:40
openstackgerritMerged openstack/airship-drydock master: (fix) Add nodeSelector to Drydock Pod  https://review.openstack.org/60269122:07
openstackgerritJenkins Uplifter proposed openstack/airship-treasuremap master: Auto chart/image uplifts to latest  https://review.openstack.org/60352022:23
openstackgerritDrew Walters proposed openstack/airship-shipyard master: plugins: Add Armada subdag/operator for helm tests  https://review.openstack.org/60323622:48
*** munimeha1 has quit IRC22:57
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: Jenkins pipeline for airship-seaworthy  https://review.openstack.org/59219022:59
openstackgerritDrew Walters proposed openstack/airship-shipyard master: plugins: Add Armada subdag/operator for helm tests  https://review.openstack.org/60323623:18
openstackgerritDrew Walters proposed openstack/airship-shipyard master: wip: actions: Add Shipyard action to test all releases  https://review.openstack.org/60323723:18

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