Tuesday, 2019-02-12

*** lemko has quit IRC00:20
openstackgerritJames Gu proposed openstack/airship-treasuremap master: Add name labels to ceph-config and horizon charts  https://review.openstack.org/63624000:25
openstackgerritJagan Mohan Kavva proposed openstack/airship-promenade master: UCP: Enable pod priority feature gate in K8s  https://review.openstack.org/63478000:42
*** seaneagan has joined #airshipit00:59
*** mrhillsman has joined #airshipit00:59
*** jayahn has joined #airshipit00:59
*** serverascode has joined #airshipit01:00
*** nishant_ has quit IRC01:23
openstackgerritBryan Strassner proposed openstack/airship-shipyard master: [WIP] Configurable Armada Retries  https://review.openstack.org/63622801:39
*** c06 has joined #airshipit04:06
openstackgerritJames Gu proposed openstack/airship-treasuremap master: Add name labels to ceph-config and horizon charts  https://review.openstack.org/63624004:29
*** c06 has quit IRC05:35
*** lemko has joined #airshipit06:30
*** georgk has joined #airshipit08:57
*** jamesgu has quit IRC09:02
*** georgk has quit IRC09:07
*** roman_g has joined #airshipit09:07
*** georgk has joined #airshipit10:10
*** georgk has quit IRC11:48
*** georgk has joined #airshipit11:59
openstackgerritRoman Gorshunov proposed openstack/airship-in-a-bottle master: Fix: docs formatting  https://review.openstack.org/63632412:34
openstackgerritRoman Gorshunov proposed openstack/airship-in-a-bottle master: Fix: docs formatting  https://review.openstack.org/63632412:39
georgkhi there! can anybody help me with getting the certificates right in an Airship deployment? We are running into SSL handshake issues...13:17
*** openstackgerrit has quit IRC13:37
*** nishant_ has joined #airshipit13:42
mattmceuenhey georgk!  sure can, would you be able to bring that up in our team meeting in a few?  I think it would actually dovetail into some Pegleg discussion we'll have13:50
mattmceuenAgenda:  https://etherpad.openstack.org/p/airship-meeting-2019-02-1213:50
georgkmattmceuen: sure13:50
*** michael-beaver has joined #airshipit13:55
mattmceuen#startmeeting Airship14:00
*** michael-beaver has quit IRC14:00
openstackMeeting started Tue Feb 12 14:00:16 2019 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Airship)"14:00
mattmceuen#topic rollcall14:00
openstackThe meeting name has been set to 'airship'14:00
*** openstack changes topic to "rollcall (Meeting topic: Airship)"14:00
mattmceuenHere's our agenda for today folks: https://etherpad.openstack.org/p/airship-meeting-2019-02-1214:00
mattmceuenPlease go ahead and add anything you'd like to discuss as folks trickle in14:01
*** michael-beaver has joined #airshipit14:01
roman_go/14:01
georgkhi14:01
b-stro/14:01
nishant_o/14:02
*** michael-beaver has quit IRC14:02
mattmceuenGM all :)14:02
*** michael-beaver has joined #airshipit14:02
mattmceuen#topic Treasuremap Snapshot14:03
*** openstack changes topic to "Treasuremap Snapshot (Meeting topic: Airship)"14:03
mattmceuenhttps://github.com/openstack/airship-treasuremap/releases14:03
michael-beavero/ Having some connection problems, hopefully don't get cut out in the middle of the meeting14:03
mattmceuengood luck michael-beaver14:03
srwilkerso/14:03
mattmceuenwe have a new cut of our approximately-monthly Airship stable release in the airship-treasuremap project14:03
mattmceuenthis is recommended for new deployments.  Please let us know if any issues are discovered in it; I know issues have been fixed in it14:04
mattmceuen#topic Armada/Tiller locking14:05
*** openstack changes topic to "Armada/Tiller locking (Meeting topic: Airship)"14:05
mattmceuenNext -- michael-beaver has been working on https://review.openstack.org/63248314:05
michael-beaverThanks mattmceuen, this has been a change i've been working on for a little while14:05
mattmceuenMichael, can you give us an overview of this work, its purpose & status?14:05
michael-beaverThe locking change is a new feature that was made mainly to keep multiple instances of armada from attempting to make conflicting actions against the cluster at the same time.14:05
michael-beaverAlthough the functionality can be used to lock down any function14:06
michael-beaverIt uses the K8s API to create a custom resource defining the lock, and continuously updates it as the function being locked is still running.14:06
michael-beaverCurrently I am waiting on reviews for it as I believe it is pretty close to being finished14:06
mattmceuenTo put you on the spot - do you happen to have an example document for the CRD handy? :)14:07
michael-beaverHaha, sorry I don't have my VM running at the moment, but at the moment it is pretty basic, it just has a field to keep track of when it was last updated14:07
michael-beaverAlthough I tried to design it so if we wanted to put more data there14:08
mattmceuenNo worries, maybe you can share it in the channel later?14:08
michael-beaverIt could easily be used to store metadata about what is currently holding the lock14:08
michael-beaverSure, I'll try to pull one up in the mean time14:08
nishant_I was going through the PS yesterday Michael,  will continue to review it today.  good work  on it. Would love to see any documentation added for this feature. :)14:09
michael-beaverThanks nishant_14:09
mattmceuenI think another good piece of doc would be, in the commit message too, why do we want multiple Armadas in the cluster!14:09
mattmceuenI think the main reason is that the single armada pod is a single point of failure, but that's not explicitly stated anywhere, and might not be obvious to someone coming in w/o the background14:10
michael-beaverSure mattmceuen, I can work on wording up something like that14:10
mattmceuenReally nice work michael-beaver -- thanks for the work on this, very cool!14:11
mattmceuenany other questions for michael-beaver on this, team?14:11
nishant_Yes I think it was also developed from security point of view. So would be good to have it mentioned in the commit message.14:12
michael-beaverThat's a good point, the other main idea of it was so we could have tiller live in the armada pod so it does not communicate over insecure channels14:12
*** levmorgan has joined #airshipit14:13
mattmceuen michael-beaver yup14:13
*** cbcg_ has joined #airshipit14:13
michael-beaverAny other questions or comments?14:14
levmorganHello, I'm here. Matt, do you still want me to go over the additions to Pegleg?14:14
mattmceuenHey levmorgan, perfect timing :)14:14
mattmceuen#topic Recent Pegleg Enhancements14:14
*** openstack changes topic to "Recent Pegleg Enhancements (Meeting topic: Airship)"14:14
mattmceuenYup, you and some other folks have been doing several interlocking pieces of work in Pegleg recently, would you ming giving us a bit of overview & status?14:15
levmorganHey, great! So, there have been three main additions to Pegleg. Certificate generation, passphrase generation, and genesis bundle generation (which is still in review).14:15
levmorganCertificate generation uses cfssl to generate certs and keypairs, which are self-signed encrypted by default.14:16
levmorganPassphrase generation has two parts. It can generate a master passphrase, which can be used to encrypt documents, or it can generate passphrase documents as specified in a passphrase catalog.14:18
mattmceuenA primary use case for those certs is for Kubernetes components & etcd -- currently those certs are generated by Promenade, but it makes sense to move that functionality into Pegleg as the external yaml management CLI14:19
levmorganYep. As for genesis bundle generation, we've pulled in the functionality from Promenade as well.14:19
mattmceuenand for the passphrases, a primary use case is for service passwords e.g. for databases and openstack service users14:19
levmorganYep, exactly.14:20
mattmceuenThat's awesome levmorgan - nice work and looking forward to using14:20
mattmceuenIf folks want some more info on Pegleg secret management, more deets can be found in this spec: https://github.com/openstack/airship-specs/blob/master/specs/approved/pegleg-secrets.rst14:21
*** ab2434_ has joined #airshipit14:21
mattmceuenThe primary use case for the certificate generation is for "cluster internal" certificates, but for a lab, pegleg could generate the externally-accessible ingress certificates as well, right levmorgan?14:21
mattmceuenwith all the caveats that come with using self-signed certificates14:22
georgkmattmceuen: if I may hook in here14:23
levmorganYep14:23
mattmceuenBasically, the pegleg passphrase catalog doc and pki catalog doc are general-purpose descriptions that tell pegleg whatever secrets you want it to generate (and encrypt), and after they're generated, they can be added to your SCM repo14:23
mattmceuenalong with other yaml14:23
mattmceuenGo for it georgk14:23
georgkwell, regarding self-signing. our folks are trying to deploy airship and are struggling with the certs14:24
mattmceuenwhat kind of issues are you seeing?14:24
georgkcurrently, teh deployment fails when b ringing up barbican becuase of an SSL handshake mismatch14:24
georgkwe assume it is due to incorrect certs14:25
georgkso, we are wondering if we can work with self-signed certs or need a full ca chain14:25
georgkis there are ¨lab¨ switch?14:25
mattmceuenhmm that's odd - barbican is not something we expose externally in airship so it seems like it might be a problem with the internal certificates that are generated -- today by promenade, soon by pegleg14:26
mattmceuenself-signed certs should be fine for that14:26
mattmceuenare you using the promenade pkicatalog to generate the certs -- I believe this is how airship-seaworthy is set up today, or are you substituting in custom certificates that you generate out-of-band?14:27
georgkafter running into this issue, we have started to generate certs out-of-band14:27
georgkhttps://hastebin.com/iriloweqif.sql14:28
mattmceuenHere's a bit of documentation on the normal certificate generation process that would be done as part of site definition: https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html#building-site-documents14:29
georgkI dont want to highjack the entire meeting - we can follow this up later14:29
mattmceuenCool - thanks for the heads up on the issue, definitely looks cert-related but I don't see any smoking gun.  We'll need to dig in a little more post-meeting I think14:30
georgkok, catch you later14:31
*** sgrasley has joined #airshipit14:31
*** sgrasley_ has joined #airshipit14:31
mattmceuen#topic New Shipyard pod structure14:31
*** openstack changes topic to "New Shipyard pod structure (Meeting topic: Airship)"14:31
*** sthussey has joined #airshipit14:31
mattmceuenb-str this is you -- enlighten us!14:31
b-strShipyard's k8s pod configuration has changed to combine several items and eliminte a few others.14:31
b-strPreviously, The following pods existed:14:31
b-strshipyard-api (1 container, Shipyard api)14:31
b-strairflow-web (1 container, Airflow api and gui)14:31
b-strairflow-scheduler (1 container, Airflow celery instance)14:31
b-strairflow-flower (1 container, Airflow celery flower instance)14:31
b-strairflow-worker (StatefulSet, 2 containers, Airflow worker; logrotate container)14:31
b-strThe first issue being resolved was that the airflow-scheduler and airflow-worker are both required to keep a workflow running.14:32
b-strIf the scheduler was updated, the workers would no longer receive new steps to process until the scheduler was running again.14:32
b-strWorse, if the scheduler was updated such that it was incompatible with the version of Airflow running in the worker, everything was effectively stopped.14:32
b-strA manual deletion of the Workers would rectify the situation, but the running workflow failed.14:32
b-strInvocation of an update_site or update_software action in Shipyard deletes/recreates the Airflow Worker after the workflow process has concluded, but this did not occur if the scheduler and worker were out of sync.14:33
b-strThe second issue was a question of need of exposure of Airflow outside the deployment of Airship, requiring further configuration of the GUI components.14:33
b-strSince Shipyard provides the entrypoint for Airship, it was decided to eliminate this exposure of the Airflow GUI components.14:33
b-strThe new pod configuration is:14:34
b-strshipyard-api (2 containers, Shipyard api; Airflow api and gui)14:34
b-strairflow-worker (StatefulSet, 3 containers, Airflow worker; logrotate container, Airflow Scheduler)14:34
b-strSuch that:14:34
b-str- The airflow api and gui container is bound to localhost, such that it is only accessible to Shipyard's api14:34
b-str- The airflow worker and scheduler are now in the same Statefulset, so they share the same lifecycle.14:35
b-str- The airflow-flower pod has been removed from deployment with Shipyard, as it was superfluous to the deployment.14:35
b-str- An airflow-scheduler pod is left in service for the upgrade process, and is removable after being on the new version.14:35
b-strFinally, another somewhat related change is to the way the Airflow image is built.14:35
b-strIt now builds the workflows from Shipyard directly into the image, as opposed to transferring them in at deployment time.14:35
b-strCommits related to Shipyard and Airflow pod restructuring:14:36
b-strhttps://github.com/openstack/airship-shipyard/commit/6b75c7119a850ee7f0c0651021076dfcf220e0f7 - Move airflow scheduler to worker statefulset14:36
b-strhttps://github.com/openstack/airship-shipyard/commit/9725b0f337ebdc7523973b50afecbf4caf2b7e6c - Build workflows into Airflow image14:36
b-strhttps://github.com/openstack/airship-shipyard/commit/a11e962eef5a5aa8f8fc15c4a324dfa6b2465061 - Move Airflow web container into Shipyard pod14:36
b-strQuestions?14:36
mattmceuen" An airflow-scheduler pod is left in service for the upgrade process" -- that's the one that packs the scheduler and worker into the same pod, right?14:37
b-stractually this is the old scheduler configuration, left in place to be the scheduler during the first upgrade14:37
b-strafter the end of the workflow, the statefulsets will be deleted, and will contain the new scheduler going forward14:38
mattmceuengotcha14:38
b-stra follow on action would be to scale the independent scheduler to 014:38
b-strand/or otherwise eliminate it14:38
mattmceuenso at some point in the future (maybe in the stable airship version that follows that follows the one that includes your change) we'll take out the old scheduler, since it serves to bridge the gap between the old scheme and the new scheme - right?14:40
* b-str yes, that's its only purpose14:40
mattmceuenawesome - THANKS for all this explanation and detail, I'll make sure a note gets sent out on the ML as this is quite valuable14:41
mattmceuenUpgrades are hard, you make them easy for the rest of us :)14:42
b-strThis has been running in Treasuremap for a few days/weeks, so it can be observed there.14:42
mattmceuenAny other questions for b-str on this topic?14:42
mattmceuenThanks Bryan14:43
mattmceuen#topic Weekly Meeting Time14:43
*** openstack changes topic to "Weekly Meeting Time (Meeting topic: Airship)"14:43
mattmceuenSeveral people have approached me over the last few weeks asking if it would be possible to adjust our weekly meeting time14:43
mattmceuenNot all of them are here (there is a correlation) but I wanted to gauge the general temperature for meeting times here14:44
* b-str earlier?14:44
* mattmceuen b-str :-|14:44
mattmceuenWould folks be amenable to this?  Maybe a couple hours later, maybe several hours later?  Or prefer a different day?  Or... ?14:44
mattmceuenI'll send something out on the ML, just looking for opinions14:45
michael-beaverI wouldn't mind it being later in the day14:45
levmorganSure, later works for me.14:45
*** aaronsheffield has joined #airshipit14:45
mattmceuenAny concerns with that?  We're spread across time zones and I don't want to make it unduly hard for anyone who wants to come regularly, if possible14:46
mattmceuenI'll propose some candidate times on the ML and see how it goes over14:47
sthusseyAnytime is fine with me as long as it is within business hours14:47
mattmceuenCool beans - more to come then14:47
mattmceuen#topic Host next week14:47
*** openstack changes topic to "Host next week (Meeting topic: Airship)"14:47
mattmceuenI'll be in a meeting during this time next week; I hope to join and multitask, but dwalt has volunteered to drive discussion14:48
mattmceuen#topic State of Airship governance docs14:48
*** openstack changes topic to "State of Airship governance docs (Meeting topic: Airship)"14:48
mattmceuenty for bringing this up georgk, this is something we need to get on top of414:48
mattmceuenalanmeadows is planning to drive this in advance of the Denver summit, so we have something to discuss there14:49
georgkok, thanks14:49
georgkI was digging through a few etherpads, but wasnt sure which one reflects the latest state14:50
mattmceuenI don't think he's here today, but I'll circle back with him to make sure his proposal is written down and shared soon14:50
mattmceuenthe joys of etherpads :)14:50
georgkyeah14:50
georgkthanks14:50
roman_gthat's not what we have in airshipit readthedocs, right?14:51
roman_gairshipit.readthedocs.io14:51
mattmceuenI think what georgk is talking about is more a proposal for formal governance.  Let me elaborate:14:52
mattmceuenAirship is one of the OSF pilot projects, and one of the things it needs to develop and get in order prior to becoming a full-fledged project is documentation of its governance -- its formal operating principles14:52
mattmceuenThings like following the Four Opens, the structure around cores and their responsibilities, the way that the project is steered, that kind of thing14:53
roman_ggot it, thanks14:53
mattmceuenIt's the kind of thing that we should get ideas / draft out for discussion way in advance14:53
georgkright14:54
mattmceuen#topic Requests for Review14:54
*** openstack changes topic to "Requests for Review (Meeting topic: Airship)"14:54
mattmceuenA few PS that nishant_ added:14:54
mattmceuen    Helm-toolkit for DB initialization14:54
mattmceuen    https://review.openstack.org/#/c/634625/14:54
mattmceuen    https://review.openstack.org/#/c/635348/14:54
mattmceuen    https://review.openstack.org/#/c/634981/14:54
mattmceuenI take it those are helm-toolkit functions for making postgres operations easier across airship (and anyone else who uses the osh postgres chart) right nishant_?14:55
nishant_So i have been working on multiple Airship components to validate if password rotation works fine.14:55
nishant_During validation I found Airship comoponents using postgre needs some modification for password rotation to work effectively14:55
nishant_and with some discussion i was advised to in turn create a helm-toolkit for DB initialization14:56
*** jamesgu has joined #airshipit14:56
nishant_which makes it easier for components to operate postgres operations easily14:56
nishant_so you are right mattmceuen14:57
mattmceuenawesome - thanks for making your work reusable, effective password rotation is critical to real life ops14:57
mattmceuenreviews please :D14:57
nishant_I am looking for any feedback and reviews on it. Thanks :)14:57
levmorganI have a couple as well:14:57
levmorganhttps://review.openstack.org/#/c/634821/ and https://review.openstack.org/#/c/613392/14:58
mattmceuengo for it levmorgan14:58
levmorganThe first one is an improvement for passphrase generation, the second one is for genesis bundle generation.14:58
levmorganThanks!14:58
mattmceuengreat - I've added them to the agenda for anyone who couldn't make it14:59
mattmceuenwith that I think we're out of time!14:59
mattmceuenThanks everyone for coming, appreciate your discussion14:59
mattmceuenHave a great day & week all15:00
mattmceuen#endmeeting15:00
*** openstack changes topic to "airshipit.org || General Review Dashboard: https://review.openstack.org/#/q/project:%255Eopenstack/airship.*+status:open,n,z"15:00
openstackMeeting ended Tue Feb 12 15:00:12 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-02-12-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-02-12-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-02-12-14.00.log.html15:00
roman_gThank you.15:00
*** levmorgan has quit IRC15:01
*** michael-beaver has quit IRC15:07
*** ianychoi has quit IRC15:07
*** ianychoi has joined #airshipit15:07
*** arunkant has joined #airshipit15:08
*** sreejithp has joined #airshipit15:11
*** ab2434_ has quit IRC15:13
*** michael-beaver has joined #airshipit15:20
*** michael-beaver has quit IRC15:25
roman_ghttps://review.openstack.org/#/c/636324/2 - minor docs formatting fix for the in-a-bottle repository; please, review. Thank you.15:25
*** openstackgerrit has joined #airshipit15:31
openstackgerritKaspars Skels proposed openstack/airship-in-a-bottle master: Move shipyard usage to build VM  https://review.openstack.org/63623915:31
openstackgerritKaspars Skels proposed openstack/airship-in-a-bottle master: Move shipyard usage to build VM  https://review.openstack.org/63623915:34
openstackgerritKaspars Skels proposed openstack/airship-in-a-bottle master: Move shipyard usage to build VM  https://review.openstack.org/63623915:36
openstackgerritKaspars Skels proposed openstack/airship-in-a-bottle master: Run shipyard from build VM (instead of Genesis)  https://review.openstack.org/63623915:38
roman_ghttps://review.openstack.org/#/c/635507/ - Add cache for results of requests to quay.io in Updater tool; Please, review. Thank you.15:46
openstackgerritchittibabu proposed openstack/airship-pegleg master: Add CLI to create Salt Key  https://review.openstack.org/63608915:48
*** roman_g has quit IRC15:57
*** roman_g has joined #airshipit15:59
georgkhi mattmceuen16:17
georgkcan I bother you once more16:17
*** mbologna has quit IRC16:22
*** georgk has quit IRC16:32
mattmceuenhey georgk absolutely :)  I'm running around a bit this morning so I apologize that responses might be a bit delayed16:33
*** michael-beaver has joined #airshipit16:58
*** peyunco has joined #airshipit17:09
*** aagate has joined #airshipit17:20
openstackgerritJagan Mohan Kavva proposed openstack/airship-promenade master: UCP: Enable pod priority feature gate in K8s  https://review.openstack.org/63478017:43
openstackgerritEvgeniy L proposed openstack/airship-treasuremap master: Configure public network in Jenkinsfile  https://review.openstack.org/63640217:56
openstackgerritMerged openstack/airship-treasuremap master: Ceph: journal partitions instead of whole disk  https://review.openstack.org/63598918:41
*** georgk has joined #airshipit18:45
*** georgk has quit IRC18:50
*** georgk has joined #airshipit18:50
*** lemko_ has joined #airshipit19:03
*** adrianreza has quit IRC19:04
*** lemko has quit IRC19:04
*** mugsie has quit IRC19:04
*** fdegir has quit IRC19:04
*** lemko_ is now known as lemko19:04
*** mugsie has joined #airshipit19:05
*** fdegir has joined #airshipit19:05
*** lemko has quit IRC19:09
*** mbologna has joined #airshipit19:16
*** georgk has quit IRC19:21
openstackgerritPRATEEK REDDY DODDA proposed openstack/airship-promenade master: This commit is to create logging section to "DEBUG" in promenade.conf and overriding log_level value in it using values.yaml  https://review.openstack.org/62915419:30
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: airskiff: Use Minikube for Kubernetes deployment  https://review.openstack.org/62261019:37
*** cbcg_ has quit IRC19:38
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: airskiff: Use Docker CE 18.06 for Minikube  https://review.openstack.org/62354919:40
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: Add cache for results of requests to quay.io in Updater tool  https://review.openstack.org/63550719:46
openstackgerritPRATEEK REDDY DODDA proposed openstack/airship-promenade master: Log Format Standardization For Promenade  https://review.openstack.org/62915419:58
openstackgerritPRATEEK REDDY DODDA proposed openstack/airship-promenade master: Log Format Standardization For Promenade  https://review.openstack.org/62915419:59
*** mbologna has quit IRC20:23
openstackgerritAlexander Hughes proposed openstack/airship-pegleg master: Add CLI to create Salt Key  https://review.openstack.org/63608920:28
openstackgerritAlexander Hughes proposed openstack/airship-pegleg master: Add CLI to create Salt Key  https://review.openstack.org/63608920:35
openstackgerritEvgeniy L proposed openstack/airship-treasuremap master: Configure public network in Jenkinsfile  https://review.openstack.org/63640221:00
*** fdegir has quit IRC21:06
*** mugsie has quit IRC21:06
*** mugsie has joined #airshipit21:06
openstackgerritchittibabu proposed openstack/airship-pegleg master: Add CLI to create Salt Key  https://review.openstack.org/63608921:14
openstackgerritSean Eagan proposed openstack/airship-armada master: Wait on all supported resource types by default  https://review.openstack.org/63644021:34
*** roman_g has quit IRC21:40
openstackgerritchittibabu proposed openstack/airship-pegleg master: Add CLI to create Salt Key  https://review.openstack.org/63608921:41
*** nishant_ has quit IRC21:52
openstackgerritdiwakar thyagaraj proposed openstack/airship-promenade master: UCP: Enable Audit Logging feature gate in K8s  https://review.openstack.org/63556822:13
*** sreejithp has quit IRC22:47
*** peyunco has quit IRC22:49
*** sthussey has quit IRC22:51
openstackgerritNishant Kumar proposed openstack/airship-specs master: (divingbell) Ansible framework  https://review.openstack.org/62822122:52
openstackgerritKaspars Skels proposed openstack/airship-treasuremap master: Configure public network in Jenkinsfile  https://review.openstack.org/63640222:55
*** michaelbeaver has joined #airshipit23:15
*** michael-beaver has quit IRC23:18
*** michaelbeaver has quit IRC23:20

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