[gentoo-soc] Fwd: 30 of May - 02 of June weekly report

[gentoo-soc] Fwd: 30 of May - 02 of June weekly report

[Christos Kotsis]

[-- Attachment #1.1.1.1: Type: text/plain, Size: 9572 bytes --]




-------- Forwarded Message --------
Subject: 	30 of May - 02 of June weekly report
Date: 	Sat, 3 Jun 2017 06:12:59 +0300
From: 	Christos Kotsis <christo.kotsi@gmail.com>
To: 	soc-admins@gentoo.org



======================================================================================================================
Please if more details are required for the entries below, tell me,
because this would be my first weekly reports.

======================================================================================================================
My first plan for the 30 of May, was to:
- Set up a card on trello, with a checklist about my firs todo task.
- Write the stage specs files for catalyst
- Crate a custom portage profile
- Create a script for filtering the spec's data and export only the
important values
- Create a script Initiate the process of creating a portage snapshot
and initiate the
building process up to stag3

There was nothing wrong with the first day, apart from the card setup
which consumed from me
some time to get used with it and the checklists

My plan for tomorrow May,31 is to:
- Create a script to combine the scripts from last day
- Add control to that script, for searching the host system for a
portage snapshot and evaluate it
- Add control options to the stage builds, to determinate if a new build
is required
- Add option for creating md5sums, and gpg sign on created items
- Create a script to extract the stage3 tarbal for:
         - Configuring it to mount /var/logs on a new drive
         - Configure it to mount /tmp on tmpfs
         - Read configuration files which will be edited by the user to
decide if it will mount
                   - /var/tmp as tmpfs
         - Create configuration files instructing initramfs to mount etc
on tmpfs
         - Create a modular kernel with overlayFS, fuser and nfs as
builtins and export it as a template
         - Create initramfs with dracut and make the system ro
         - Create a scrip to archive the system back to a tarball,
create md5sums and gpg sign it
         - Install the system to a machine and test if the it runs with
/etc,/var/logs,/tmp as tmpfs

======================================================================================================================
My plan for  May,31 was to:
- Create a script to combine the scripts from last day
- Add control to that script, for searching the host system for a
portage snapshot and evaluate it
- Add control options to the stage builds, to determinate if a new build
is required
- Add option for creating md5sums, and gpg sign on created items
- Create a script to extract the stage3 tarbal for:
         - Configuring it to mount /var/logs on a new drive
         - Configure it to mount /tmp on tmpfs
         - Read configuration files which will be edited by the user to
decide if it will mount
                   - /var/tmp as tmpfs
         - Create configuration files instructing initramfs to mount etc
on tmpfs
         - Create a modular kernel with overlayFS, fuser and nfs as
builtins and export it as a template
         - Create initramfs with dracut and make the system ro
         - Create a scrip to archive the system back to a tarball,
create md5sums and gpg sign it
         - Install the system to a machine and test if the it runs with
/etc,/var/logs,/tmp as tmpfs

Items I did not complete:
- Create a script to archive the system back to a tarball, create
md5sums and gpg sign it.
- Read configuration files which will be edited by the user to decide if
/var/tmp will be mounted as tmpfs

Failure for the above 2 items was simple time related. However I created
an extra step
which was planned for tomorrow.

- Create the modules and built dracut with those, to mount the rootfs as
ro with /etc, /tmp
and /var/logs mounted as tmpfs directly from the initramfs.

My plan for tomorrow 01 Jun is to:
- Further combine the above to work well with the main-menu script {Not
the parts about initramfs}
- Finish the chroot main script which will
    - Configure portage
    - Configure the locale scripts
    - Configure consolefont
    - Configure /etc/conf.d/network
    - Configure the runlevel scripts
    - Configure the Install custom packages scripts
    - Configure the world rebuild scripts if a pre-compiled tarball in
selected by the user
    - Set the portage profile
    - Configure the scripts to the symlinks, bind, tmpfs  and overlayFS
entries on the system
    - Create the scripts to inject custom files to the system
    - Configure the scripts to prepare the chroot environment and copy
configuration files
    - Configure the script to initiate the chroot main script selected
method ( catalyst,pre-compiled )
    - Create the entries to read the device info, mount a simple usb
stick and create the indicated filesystem
    - Create the entries to mount and build the modular kernel and
dracut initramfs that
was done manually today.
    - Create the entries to label the usb stick as BOOTB, which will
instruct the dracut
in the future to remember that the usb stick is there for the purpose of
helping with establishing the real boot
LABEL=BOOT that will line in an internal partition.

======================================================================================================================
My plan for 01 of June was:
- Further combine the above to work well with the main-menu script {Not
the parts about initramfs}
- Finish the Chroot main script which will
    - Configure portage
    - Configure the locale scripts
    - Configure consolefont
    - Configure /etc/conf.d/network
    - Configure the runlevel scripts
    - Configure the Install custom packages scripts
    - Configure the world rebuild scripts if a pre-compiled tarball in
selected by the user
    - Set the portage profile
    - Configure the scripts to the symlinks, bind, tmpfs  and overlayFS
entries on the system
    - Create the scripts to inject custom files to the system
    - Configure the scripts to prepare the chroot environment and copy
configuration files
    - Configure the script to initiate the chroot main script selected
method ( catalyst,pre-compiled )
    - Create the entries to read the device info, mount a simple usb
stick and create the indicated filesystem
    - Create the entries to mount and build the modular kernel and
dracut initramfs that was done manually today.
    - Create the entries to label the usb stick as BOOTB, which will
instruct the dracut in the future
to remember that the usb stick is there for the purpose of helping with
establishing the real boot
LABEL=BOOT that will line in an internal partition.

All items where completed, however more testing is needed on the initramfs

My plan for tomorrow is:
-Upgrade the functions of initramfs (more essential packages to aim with
the objectives)
-Check the stability from the builted initramfs
-Create hook script for mounting the LABELS { eg mounting LABLE=SYSFS}
-Create hook script for creating partition interfaces
-Create hook script for making filesystems
-Create hook script for managing LABELS
-Create hook script for chrooting in a mounted drive, and initiate the
basic chroot_init script there.

I don't know if I can add more options here, because initramfs is not a
field that I can play with ease.
However if the above items get done in time, I'll attempt to:
-Enable early networking on the initramfs
-Create hook script for for establishing connection with a local machine
-Create hook scripts to fetch configuration files from that machine, and
save them on a local drive
-Create hook scripts to read and export the above configuration files

======================================================================================================================

My plan for 02 of June was:
-Upgrade the functions of initramfs (more essential packages to aim with
the objectives)
-Check the stability from the builted initramfs
-Create hook script for mounting the LABELS { eg mounting LABLE=SYSFS}
-Create hook script for creating partition interfaces
-Create hook script for making filesystems
-Create hook script for managing LABELS
-Create hook script for chrooting in a mounted drive, and initiate the
basic chroot_init script there.

I created the dracut modues for the above objectives, however the size
of the generated image is big since I included many files to aid the
above steps. I guess I'LL have to remove some of them, or even apply
different method for the objective, to avoid such a size ~120MB.

My plan for Monday is:
    -Reduce the size of the initramfs
    -Write documentations a general introduction to the project's directory:
            -Structure
            -Files
                   -dist.d directory
                   -config.d directory
                    -configuration files
                    -functions
                    -main scripts
  -Create scripts for alternative build with a precompiled gentoo
tarball, instead of catalyst
  -Create scripts for alternative build using the live system that will
emerge -e with ROOT=/path/to/dist.d/stage3-version and chroot it for
configuration
  -Fix the custom portage profile & include new make.defaults and
package.use files for it

======================================================================================================================


[-- Attachment #1.1.1.2: Type: text/html, Size: 10688 bytes --]

[-- Attachment #1.1.2: 0x13E499BA.asc --]
[-- Type: application/pgp-keys, Size: 3213 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]