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

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

[Alice Ferrazzi]

Summary:

elivepatch:
* improved code as per mentor review
* fixing uuid design
    moved the uuid generating to the client and read rfc 4122 that states:
    "A UUID is 128 bits long, and requires no central registration process."
* made regex function for checking the format of uuid is actually correct.
* made elivepatch multi-threading

kpatch-build:
* Sended pull request to kpatch for adding dynamic output folder option
    https://github.com/dynup/kpatch/pull/718
* Sended pull request to kpatch for small style fix
    https://github.com/dynup/kpatch/pull/719

-----------------------------------------
day 32:

`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

client checkers:
* used os.path.join for ungz function
* implemented temporary folder using python tempfile

`what i will do next time?`

* testing and improving elivepatch

-----------------------------------------
day 31:

`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

Dispatcher.py:

* fixed comments
* added static method for return the kernel path
* Added todo
* fixed how to make directory with uuid

livepatch.py
* fixed docstring
* removed sudo on kpatch-build
* fixed comments
* merged ebuild commands in one on build livepatch

restful.py
* fixed comment


`what i will do next time?`

* testing and improving elivepatch


-----------------------------------------
day 30:
`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

* fixing uuid design

moved the uuid generating to the client and read rfc 4122

that states
"A UUID is 128 bits long, and requires no central registration process."

* made regex function for checking the format of uuid is actually correct.


`what i will do next time?`

* testing and improving elivepatch


-----------------------------------------
day 29:



`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

* Refactored for code clarity [not finished yet]
* Sended pull request to kpatch for adding dynamic output folder option
    https://github.com/dynup/kpatch/pull/718
* Sended pull request to kpatch for small style fix
    https://github.com/dynup/kpatch/pull/719

`what i will do next time?`

* testing and improving elivepatch

-----------------------------------------
day 28:

`What was my plan for today?`

* testing and improving elivepatch

`What i did today?`

* Testing elivepatch with multi threading
* Removed check for uname kernel version as is getting the kernel
   version directly from the kernel configuration file header.
* Starting kpatch-build under the output folder
   Because kpatch-build is making the livepatch under the $PWD
   folder we are starting it under the uuid tmp folder and we
   are getting the livepatch from the uuid folder. this is
   usefull for dealing with multi-threading
* Added some helper function for code clarity [not finished yet]
* Refactored for code clarity [not finished yet]

For making elivepatch multithread we can simply change app.run() of
flask with app.run(threaded=True).
This will make flask spawn thread for each request
(using class SocketServer.ThreadingMixIn and baseWSGIserver)1, but also if is
working pretty nice, the suggested way of threading is probably using
gunicorn or
uWSGI.2
maybe like using flask-gunicorn: https://github.com/doobeh/flask-gunicorn


`what i will do next time?`

* testing and improving elivepatch

[1] https://docs.python.org/2/library/socketserver.html#SocketServer.ThreadingMixIn
[2] http://flask.pocoo.org/docs/0.12/deploying/

-- 
Thanks,
Alice Ferrazzi

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