Linux Foundation Wiki

project collaboration site

User Tools

Site Tools


civilinfrastructureplatform:journal

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
civilinfrastructureplatform:journal [2018/08/10 14:59]
rajmarshall
civilinfrastructureplatform:journal [2018/10/22 06:01] (current)
SZLin
Line 1: Line 1:
 ====== CIP journal 2018 ====== ====== CIP journal 2018 ======
  
-This is the journal followed by CIP developers to keep track of the work being done on behalf of CIP.It starts in 2018Q2.+This is the journal followed by CIP developers to keep track of the work being done on behalf of CIP. It starts in 2018Q2
 + 
 +===== October ===== 
 + 
 +==== Sunday 2018/10/21 ==== 
 + 
 +=== toscalix === 
 + 
 +   * TSC f2f meeting in Edinburgh, UK. 
 +      * Presentation of BuildStream:​ 10 min. 
 +      * Ben H., Emmet and John joins the TSC meeting. 
 + 
 +=== SZ Lin (林上智) === 
 +   * Joined TSC f2f meeting via zoom 
 + 
 +==== Friday 2018/10/19 ==== 
 + 
 +=== toscalix === 
 + 
 +   * Preparation of the TSC meeting 
 +      * Preparation of the BuildStream slide deck. 
 +      * Review of the agenda. 
 + 
 +=== rajm === 
 + 
 +   * Reviewed the wiki and made minor changes. 
 +   * Sent an email with a report on progress since June so it can be reported on at ELC-E. 
 +   * Ran a BBB  health check successfully,​ email to the list. 
 +   * Ran an iwg20m health check successfully,​ email to the list. 
 + 
 +==== Thursday 2018/10/18 ==== 
 + 
 +=== rajm === 
 + 
 +   * Tested lava-docker on our guest network - which gives ip addresses 172.16* matching the addresses docker uses but I'm still getting failures in U-Boot. 
 +   * 1:1 with toscalix. 
 +   * Ran a fresh provision for week 42 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]]. 
 +   * Participated in cip-dev IRC meeting. 
 +   * Ran a BBB  health check successfully,​ email to the list. 
 +   * Ran an iwg20m health check successfully,​ email to the list. 
 + 
 +==== Wednesday 2018/10/17 ==== 
 + 
 +=== rajm === 
 + 
 +   * Discussion with mungaip on getting artifacts from host with LAVA running in docker. 
 +   * Still issues running from home with lava-docker - I'll check with the CT guest network tomorrow. 
 +   * Ran an BBB health check successfully,​ email to the list. 
 + 
 +==== Tuesday 2018/10/16 ==== 
 + 
 +=== rajm === 
 + 
 +   * Ran an iwg20m health check successfully,​ email to the list. 
 +  
 + 
 +==== Friday 2018/10/12 ==== 
 + 
 +=== rajm === 
 + 
 +   * A provisioned box is now ready to be uploaded but having issues connecting to AWS. 
 +   * Ran an iwg20m health check successfully,​ email to the list. 
 +   * Ran a BBB health check successfully,​ email to the list. 
 + 
 +==== Thursday 2018/10/11 ==== 
 + 
 +=== rajm === 
 + 
 +  * Participated in cip-dev IRC meeting. 
 +  * Ran a BBB health check successfully,​ email to the list. 
 +  * Ran an iwg20m health check successfully,​ email to the list. 
 + 
 + 
 + 
 +==== Tuesday 2018/10/09 ==== 
 + 
 +=== rajm === 
 + 
 +  * Ran a fresh provision for week 40 (a couple of days late!) [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]]. 
 +  * Ran a BBB health check successfully,​ email to the list. 
 +  * Ran an iwg20m health check successfully,​ email to the list. 
 + 
 +=== toscalix === 
 + 
 +   * Organising the trip to ELCE 2018.  
 +      * Asked for confirmation about the TSC f2f meeting starting time and location (room). 
 + 
 + 
 +==== Friday 2018/10/05 ==== 
 + 
 +=== rajm === 
 + 
 +  * Sent fortnightly progress report to cip-dev 
 +  * Creating a provisioned box (of latest master) for upload to the website. 
 +  * Now that the iwg20m MR is merged I've closed the associated [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​186| issue 186]]. 
 +  * Added [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​202|#​202]] so that file headers get checked and any necessary licence information added. 
 +  * Ran a BBB health check successfully,​ email to the list. 
 +  * Ran an iwg20m health check successfully,​ email to the list. 
 + 
 + 
 + 
 +==== Thursday 2018/10/04 ==== 
 + 
 +=== rajm === 
 + 
 +  * Team meeting. 
 +  * Following bwh's approval [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​63|MR 63]] is now merged. 
 +  * Commented on Nguyen'​s comment on [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​63|MR 63]] 
 +  * Participated in cip-dev IRC meeting. 
 +  * Ran an iwg20m health check successfully,​ email to the list. 
 +  * Ran a BBB health check successfully,​ email to the list. 
 + 
 + 
 +==== Tuesday 2018/10/02 ==== 
 + 
 +=== rajm === 
 + 
 +  * Tried running lava-docker on my (home) ubuntu which gave more issues. 
 +  * Clarification of when iwg20m health checks will be run to cpaterson. 
 +  * Ran a BBB health check successfully,​ email to the list. 
 + 
 + 
 +==== Monday 2018/10/01 ==== 
 + 
 +=== rajm === 
 + 
 +  * Tried running lava-docker away from the Codethink network but that still failed.  
 +  * I tried to replicate the wifi issue on the BBB [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​200|#​200]] but failed to do so - the test worked. 
 +  * Unable to run an iwg20m health check this morning as I'm working from home - I'll run this again on Thursday. 
 +  * Ran a BBB health check successfully,​ email to the list. 
 + 
 +=== SZ Lin (林上智) === 
 +  * Create [[civilinfrastructureplatform:​linux-4.4.y|wiki page]] for stable kernel review. 
 +  * Confirmed that 4.4.y-stable is *NOT* vulnerable with [[https://​thehackernews.com/​2018/​09/​linux-kernel-vulnerability.html|this security bug]] (Fixed in 86949eb96466e "exec: Limit arg stack to at most 75% of _STK_LIM"​) 
 + 
 +=== toscalix === 
 + 
 +   * Attended to the TSC meeting 
 +      * I have no objections of using patchwork at CIP. 
 +         * Does Ben H. has any objections?​ 
 +      * Raised a question about the TSC meeting schedule. It is not confirmed yet. 
 +      * A meeting of the Debian Kernel team will take place [[https://​www.mail-archive.com/​debian-kernel@lists.debian.org/​msg112588.html|tomorrow]]. It is interesting for CIP if the discussion about the next kernel is part of the agenda.  
 +      * During ELCE it would be ideal to know the ddates for the f2f TSC meeting around Embedded World 2018. 
 + 
 +===== September ===== 
 + 
 +==== Friday 2018/09/28 ==== 
 + 
 +=== rajm === 
 + 
 +  * Some discussion with bwh as to whether a move to use the zImage is appropriate.  
 +  * A fresh provision of the B@D has been done and the iwg20m build and health check worked. 
 +  * An email has been sent to cip-dev thanking Nguyen and as a notification of the iwg20m advance. 
 +  * A [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​63|MR]] has been created for the iwg changes. 
 +  * I see that if the host is suspended, on reawakening the clock is correct - this is with Vagrant 2.1.2 so I've closed [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​187|#​187]] 
 +  * Ran an iwg20m health check successfully,​ email to the list. 
 +  * Ran a BBB health check successfully,​ email to the list. 
 + 
 + 
 +==== Thursday 2018/09/27 ==== 
 + 
 +=== rajm === 
 + 
 + 
 +  * 1:1 with toscalix. 
 +  * The iwg20m appears to work consistently if the device-type is changed so that LAVA doesn'​t attempt to convert to a uImage and uses bootz. [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​186|#​186]] has been updated. 
 +  * Attended the cip-dev IRC meeting. 
 +  * Ran an IWG20M health check successfully,​email to the list. 
 +  * Ran a BBB health check successfully,​email to the list. 
 + 
 +=== SZ Lin (林上智) === 
 +  * Attended the cip-dev IRC meeting. 
 + 
 +==== Wednesday 2018/09/26 ==== 
 + 
 +=== rajm === 
 + 
 +   * I tried amending renesas-iwg20m.jinja2 in B@D and using the zImage kernel but unsucessfully. 
 +   * There are differences between beaglebone-black.jinja2 in B@D and the lava-docker version, I attempted to make the lava-docker version like our version but so far it still fails to health check. The tftp serverip is rather different in lava-docker and wonder if our network settings are causing the issue. 
 +   * Updated iwg20m to use a uImage as per Nguyen'​s instructions on [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​186|#​186]] ran 5 tests (one health check the others using lavacli) and all worked. Added a notify section and re-ran the health check which also worked, if the daily health check also runs ok tomorrow, I'll close the issue and update the wiki with instructions. 
 +   * Ran a BBB health check successfully,​email to the list. The email from last Friday never appeared, I don't know why - it left the VM but didn't reach the list server, maybe there was a connection with the office power cut we had that morning? 
 + 
 +==== Friday 2018/09/21 ==== 
 + 
 +=== rajm === 
 + 
 +   * Sent email listing progress in weeks 30-38 to the cip-dev email list. 
 +   * New section on [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​ciptestingreferencetestcases#​test-7use-lavacli-utility|lavacli]] added to wiki. 
 +   * lava-tool is deprecated, so I've manually installed lavacli and run a test successfully. 
 +   * I've added a note to the LAVA notification section on the wiki that IRC pings on Freenode are not working at the moment due to their SPAM avoidance methods. 
 +   * Ran a BBB health check successfully,​ still waiting for the email to appear on the list. 
 + 
 + 
 +==== Thursday 2018/09/20 ==== 
 + 
 +=== rajm === 
 + 
 +   * Ran a fresh provision for week 38 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]]. 
 +   * Met in the team meeting. 
 +   * Pushed a new version of docker-provision.sh to [[https://​gitlab.com/​cip-project/​cip-testing/​kernelci-docker|the CIP kernelci-docker]] where the initramfs build works - it uses init-example from b@d. 
 +   * Attended the cip-dev IRC meeting. 
 +   * Ran a BBB health check successfully with an email to the list. 
 + 
 + 
 +=== toscalix === 
 + 
 +   * During the IRC cip-dev meeting I checked the state of the TSC minutes being published since there were a couple of actions points to escalate topics there. Instead of any of us providing outcome of the TSC discussions,​ we should just simply refer to the minutes. 
 +     * There are no minutes published sinec January 2018 
 +     * I sent a mail to cip-dev to have them published.  
 + 
 +==== Wednesday 2018/09/19 ==== 
 + 
 +=== rajm === 
 + 
 +   * docker-provision.sh builds initramfs and copies it to the kernelci docker in the correct location (or at least a http accessible location) so I've ticked the relevant box on [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]]. 
 +   * I've added a docker-provision.sh to [[https://​gitlab.com/​cip-project/​cip-testing/​kernelci-docker|the CIP kernelci-docker]] and will add init-example shortly (or maybe it should take that from B@D?). 
 +   * The 3rd party docker repos mirrorings e.g [[https://​gitlab.com/​cip-project/​3rd-party/​kernelci-docker-mirror|kernelci]] are still failing. 
 +   * Ran a (lava-tool) test of BBB using a wifi connect for Vagrant on the host  to attempt to replicate [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​200|#​200]] but it worked ok. 
 +   * Ran a BBB health check successfully with an email to the list. 
 + 
 +==== Monday 2018/09/17 ==== 
 + 
 +=== toscalix === 
 + 
 +   * Participated at the TSC meeting 
 +      * Provided a status report about kernel maintenance final tasks and handover. 
 + 
 +=== SZ Lin (林上智) === 
 +  * Attended TSC meeting. 
 +      * Reported status of kernel IRC meeting 
 + 
 +==== Friday 2018/09/14 ==== 
 + 
 +=== rajm === 
 + 
 +  * Response to [[https://​github.com/​kernelci/​lava-docker/​issues/​45|issue 45]] from khilman suggesting either a U-Boot upgrade or a lab/​networking issue.  
 +  * 1:1 with toscalix.. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +==== Thursday 2018/09/13 ==== 
 + 
 +=== rajm === 
 + 
 +   * Demo of the existing state of containerisation with toscalix. 
 +   * Added tick box to [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]] so that emailed notifications get thought about. IRC notifications don't work now because of the freenode anti-spam +r settings. 
 +   * Participated in team meeting. 
 +   * Multiple IP address setting documentation is now on the board page - it has been for some time - I just wasn't finding it! (See yesterday'​s comment for the original mention.) 
 +   * Fixed an incorrect internal section number cross reference in "B@D Setup and Configuration (2/​5)"​ 
 +   * Raises my lava-docker issue at [[https://​github.com/​kernelci/​lava-docker/​issues/​45|issue 45]] having retried the BBB health check with docker against B@D this morning. 
 +   * Realised the default (new) health check for cip28 was missing a notify section, added that and re-ran the check and the email went to the list.  
 +   * Attended the cip-dev IRC meeting. 
 +   * Built cip28 on B@D and a successful health check - but no email to list. 
 + 
 +==== Wednesday 2018/09/12 ==== 
 + 
 +=== rajm === 
 + 
 +  * I need to ensure that the connect scripts are passed to the correct container in lava-docker. connectBBB.sh needs to be copied to lab-slave-0. Trying lava-docker with b@d as a provider of builds still times out when trying to talk to the tftp server. 
 +  * Note that editing the health check on the host with emacs if it produces a backup file (ending in '​~'​) makes the built docker unusable! 
 +  * The section on multiple IP addresses seems to have gone missing from the wiki (or I'm not finding it!) investigating. 
 +  * Opened [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​200|#​200]] so that the networking issues that have been seen in some situations get addressed. 
 +  * Ran a BBB health check successfully with an email to the list - though that's taking a little time to get through. I had issues running B@D using the wifi connection and Ihad to revert to using ethernet to get the healthcheck to run. Email now received ok. 
 + 
 + 
 +==== Friday 2018/09/07 ==== 
 + 
 +=== rajm === 
 + 
 +  * Added some container todo points to tickboxes in [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]]. 
 +  * 1:1 with toscalix. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +=== toscalix === 
 + 
 +  * Created the kernelci-docker and lava-docker repos. 
 +  * Created the kernelci-docker-mirror and lava-docker-mirror repos in 3rd-party subgroup. 
 + 
 + 
 +==== Thursday 2018/09/06 ==== 
 + 
 +=== rajm === 
 + 
 +  * Added another 2 points from [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|192]] to yesterday'​s list. 
 +  * Added PR [[https://​github.com/​lucj/​kernelci-docker/​pull/​24|24]] for kernelci-docker. 
 +  * Attended the cip-dev IRC meeting. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 + 
 +==== Wednesday 2018/09/05 ==== 
 + 
 +=== rajm === 
 + 
 +  * I think the following need resolving to get the docker implementation of B@D running: 
 +      *  Get lava-docker into kernelci swarm. 
 +      * FILE_SERVER_URL = "​http://​127.0.0.1:​8082/"​ in kernelci flask though maybe this should be in upstream? 
 +      * Create gitlab repos for our mirrors. 
 +      * We need a mechanism for updating health check to use the most recent build of kernel. 
 +      * We should build initramfs on host and then copy to kernelci-docker as part of (initial) provisioning. 
 +      * Add beaglebone to the provision and the health check. 
 +      * Also give the lava docker a history (as kernelci-docker has)? 
 +      * Update kernelci-build automatically on host so that the key matches the currently running kernelci docker. 
 +      * Add installation of expect to lava-docker and our login script for the BBB. 
 +      * Licence headers need adding. 
 +  
 +  * Confirmed that lava-docker built on my home desktop without the network problems I've been experiencing. So I assume any problems are one of ubuntu (at home) vs debian, my laptop network settings, corporate network settings. May not be relevant as the lava-docker will need merging into the kernelci swarm which doesn'​t experience this problem. 
 +  * Ran a fresh provision for week 36 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]]. I had to run QEMU twice to get that to pass and the output showed a slow install of packages (apache) that I don't remember seeing before. I will check against the example output on the wiki. Check made and output is as before, I suspect a slow internet connection made that output scroll slowly and therefore be more apparent. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +==== Monday 2018/09/03 ==== 
 + 
 +=== SZ Lin (林上智) === 
 +  * Attended TSC meeting. 
 +    * Listed candidates for CIP kernel maintenance.
  
 ===== August ===== ===== August =====
  
-==== Thursday 2018/08/10 ====+==== Friday 2018/08/31 ==== 
 + 
 +=== rajm === 
 + 
 +   * Added a cp of a local beaglebone-back.yaml into the lava docker to Dockerfile, however it is not managing to retrieve the build from the kernelci container. ​ In addition consideration needs to be given as to where the initramfs is to be built and stored. 
 +   * I don't see the networking failures when starting containers with docker-compose,​ I think the lava-docker will need setting up with compose anyway so I expect this error will cease to matter. Reading up on '​compose'​. No, it already uses compose, it's swarm mode that's different. 
 +   * Ran a BBB health check successfully with an email to the list. 
 + 
 +==== Thursday ​2018/08/30 ==== 
 + 
 +=== rajm === 
 + 
 +   * 1:1 with toscalix. 
 +   * I've modified my local copy of flask_settings to set FILE_SERVER_URL and am now able to retrieve builds - see [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​197|#​197]]. 
 +   * Initially wasn't seeing builds appear in the kernelci docker - but there were in the image - will keep a watch on this! 
 +   * Will look at sangorrin'​s commits to the kernelci docker wrt being unable to download builds but I think from his comments that it's a general problem. 
 +   * Attended the cip-dev IRC meeting. 
 +   * Ran a BBB health check successfully with an email to the list. 
 +   * Returned from holiday. 
 + 
 +=== toscalix === 
 + 
 +   * Participated in the cip-de IRC meeting 
 +      * Still pending the request to bwh for advice about the creation of a group account in kernel.org bwh advice is important because we assume that to create it we will need support from him. 
 +      * 4.19 seems to be the next LTS kernel. When is expected to have a decision/​announcement from Debian about the next LTS kernel? 
 +      * [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]] is the ticket to follow if you are interested in rajm work about containerization of B@D 
 +      * The testing infra is in place: https://​kernelci.ciplatform.org/​ 
 +         * An admin is required. Suggested to discuss it at TSC level since there will be a person assigned. This work cannot be on best effort basis. 
 +   * Implemented the Gitlab roles policy at group and subgroup level. It is not for me to decide how to apply it at repo level. That correspond to the maintainers of each repo. 
 +      * Informed about the execution of the policy. 
 +      * Suggested to move cip-core repo to a new subgroup. 
 + 
 +=== SZ Lin (林上智) === 
 + 
 +  * Attended cip-dev IRC meeting. 
 +      * Sent the overlayfs backport patches 
 + 
 + 
 + 
 +==== Thursday 2018/08/23 ==== 
 + 
 +=== toscalix === 
 + 
 +   * Participated in the weekly cip-dev IRC meeting. 
 +      * I asked where the new kernel repo will be hosted, since the current one, in kernel.org, is under bwh personal account, like the -rt one is under Daniel W.'s.  
 +         * Asked through cip-dev to bwh for advice. 
 +   * Working on a proposal for the Linux Foundation about the new role bwh will play as mentor of the kernel maintenance team.  
 + 
 +=== SZ Lin (林上智) === 
 + 
 +  * Attended cip-dev IRC meeting. 
 + 
 +==== Wednesday 2018/08/22 ==== 
 + 
 +=== rajm === 
 + 
 +   * Ran a fresh provision for week 34 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]]. 
 +   * Reviewing a document prepared by mungaip of the steps he needed to get B@D provisioned behind the Renesas proxy. The intention is to add an item to the Workarounds section. 
 +   * Ran a BBB health check successfully with an email to the list. 
 + 
 +==== Monday 2018/08/20 ==== 
 + 
 +   * TSC meeting 
 +      * The proposal I did to manage the maintainers permissions on Gitlab.com repos was approved. Now we need to implement it. 
 + 
 +=== SZ Lin (林上智) === 
 + 
 +  * Attended cip-dev IRC meeting. 
 + 
 +==== Friday 2018/08/17 ==== 
 + 
 +=== rajm === 
 + 
 +  * Responded to mungaip'​s latest state in [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​195|#​195]] - his problems appear to be proxy related, I'll check up on various proxy related issues ticketed previously (that'​s [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​99|#​99]]) though his issues are slightly different; #99 suggests there should be an item about proxy problems in Known issues which hasn't happened! 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +==== Thursday 2018/08/16 ==== 
 + 
 +=== rajm === 
 + 
 +  * Various attempts to get the docker images to start without networking failures. Will investigate swarm mode as kernelci in the version I'm using (lucj) doesn'​t have this problem - and the master version does! 
 +  * I have installed vagrant 1.9.1 and  virtualbox 5.1.38 (the identical versions to mungaip ) and install_dependencies.sh runs successfully for me. 
 +  * Created [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​195|#​195]] and [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​196|#​196]] to address the issue apparently with Vagrant 1.9.1 and documentation on how to install a version of virtualbox that cooperates with that version. 
 +  * Emailed Operations to hand back the Windows 10 machine that we've been using to test B@D in that environment. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +=== SZ Lin (林上智) === 
 + 
 +  * Attended cip-dev IRC meeting. 
 + 
 +==== Wednesday 2018/08/15 ==== 
 + 
 +=== rajm === 
 + 
 +  * Trying to test mungaip'​s issue with Vagrant 1.9.1 (the default version in Debian stretch) which doesn'​t work well with the version of VirtualBox also provided by stretch. 
 +  * 1:1 with toscalix. 
 +  * Discussion with mungaip on IRC about the issues he's having with provisioning a B@D instance. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +=== toscalix === 
 + 
 +   * Meeting with Ben Hutchings to brainstorm and prepare the hand over to the new maintainer. 
 +   * Ben informs me about l1ft. I comment on IRC Ben is on it. 
 + 
 + 
 +==== Friday ​2018/08/10 ====
  
 === rajm === === rajm ===
civilinfrastructureplatform/journal.1533913173.txt.gz · Last modified: 2018/08/10 14:59 by rajmarshall