[gentoo-soc] Google Summer of Code summary week 09

[gentoo-soc] Google Summer of Code summary week 09

[Alice Ferrazzi]

___Google Summer of Code summary week 09___


What I did in this week 09 summary:

elivepatch:

* Fix return message for cve option
* Added different configuration example [4.9.30,4.10.17]
* Catch gentoo-sources not available error
* Catch missing livepatch errors on the client
- working on incremental patch features design and implementatio
    - putting patch files under /tmp/elivepatch (for now)
    - ordering patch by numbers
    - cleaning folder when the machine is restarted
    - sending the patches to the server in order
- cleaning client terminal output by catching the exceptions
- working on making the code for sending a unknown number of files with Werkzeug

Kpatch work:
- Started to make the incremental patch feature
- Tested kpatch for permission issue


Plan (ordered by importance):

- incremental patch tracking on the client side
- CVE security vulnaribility checker
- dividing the repository [optional]
- ebuild [optional]
- documentation [optional]
- modularity [optional]


---------------------------------------------------
day 37

`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

* Fix return message for cve option
* Added different configuration example [4.9.30,4.10.17]
* Catch gentoo-sources not available error
* Catch missing livepatch errors on the client

Tested kpatch with patch for kernel 4.9.30 and 4.10.17 and it worked
without any problem.
I checked with coverage for see which code is not used.
I think we can maybe remove cve option for now as not implemented yet
and we could use a modular implementation of for it, so the configuration
could change.
We need some documentation about elivepatch on the gentoo wiki.
We need some unittest for making development more smooth and making it
more simple to check the working status with github travis.

I talked with kpatch creator and we got some feedback:

“this project could also be used for kpatch testing :)
imagine instead of just loading the .ko, the client were to kick off
a series of tests and report back.”

“why bother a production or tiny machine when you might have a
patch-building server”


`what i will do next time?`

* testing and improving elivepatch

---------------------------------------------------
day 38

`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

Meeting with mentor summary

What we will do next:
- incremental patch tracking on the client side
- CVE security vulnaribility checker
- dividing the repository
- ebuild
- documentation [optional]
- modularity [optional]

Kpatch work:
- Started to make the incremental patch feature
- Tested kpatch for permission issue


`what i will do next time?`

* testing and improving elivepatch
* Investigating the missing informations in the livepatch
---------------------------------------------------
day 39

`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

Meeting with mentor summary

elivepatch work:
- working on incremental patch features design and implementatio
    - putting patch files under /tmp/elivepatch (for now)
    - ordering patch by numbers
    - cleaning folder when the machine is restarted
    - sending the patches to the server in order
- cleaning client terminal output by catching the exceptions


`what i will do next time?`

* testing and improving elivepatch
---------------------------------------------------
day 40

`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

Meeting with mentor summary

elivepatch work:
- working on incremental patch manager
- cleaning client terminal output by catching the exceptions

Making and Testing patch manager


`what i will do next time?`

* testing and improving elivepatch
---------------------------------------------------
day 41

`What was my plan for today?`

* working on incremental patches for elivepatch

`What i did today?`

elivepatch work:
- working on making the code for sending a unknown number of files with Werkzeug

Making and Testing patch manager


`what i will do next time?`

* working on the incremental patches for elivepatch

-- 
Thanks,
Alice Ferrazzi

Gentoo Kernel Project Leader
Mail: Alice Ferrazzi <alicef@gentoo.org>
PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A