Update openbmc initfs to add temporary run from RAM #200
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The intention was to test the flag variable set when proc was mounted earlier in the script, not the constant string containing the name of the variable. The unnecessary unmount is not noticeable when a normal shutdown or reboot is being performed while executing after systemd, but results in a less usable environment when invoked manually. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
The desired system call is not an ioctl but tcsetattr with second parameter TCSADRAIN. Reported-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Milton Miller <miltonm@us.ibm.com>
The test command is documented as taking = and not == to test two strings for equality. While both appear to work use the documented comparison operator. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Complain if the update program is missing if flash update images are present. This is similar to the message in root and will inform a serial console reader why the update images are not being applied. The update script is copied from the initramfs to the run tmpfs ram file system. It is built and packaged with the init and shutdown script. It would have been removed, unpackaged, or init changed for unknown reasons by root or the build system for this to occur. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
While both are the same directory via bind mount when shutdown is executing from systemd use the full pathname to the script. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
We don't need to hold saved files for a future restore. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Because update now returns to shutdown for the final halt or reboot system call it does not need to handle systemd arguments. Instead update is being invoked from multiple environments, and further environments will need alternate behaviors. Add a code to start parsing the command line. Start wtih a flag to clean the saved files at the end of the update process. This will reclaim the space and prevent stale saved files from being restored without requiring the calling script to know the location of the saved files directory. Parse true and complement actions in case we decide to change the defaults later. For now keep the user feature of calling update, flashing some files by hand, then a final call to update with a possibly empty image file will have the original saved files merged into the rwfs. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Allow the save and/or restore of whitelisted files to be suppressed. This reduces the noise and possible problems trying to mount the read-write filesystem read-write when its dirty. The filesystem may be cleaned or repaired between the backup and restore. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Let the copy loop execute zero times instead of checking if the whitelist is empty. Suppressing the mount and copying the files can be achieved via command line options. This removes a condition and prepares for splitting the whitelist into component files with support for commented out lines. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Find the whitelist under /run/initramfs directory instead of looking in root directory. This results in the whitelist always existing and being the same instance (copy) in all environments. Currently the update script is invoked from two places: from shutdown, where systemd bind-mounted the initramfs directory on itself and made it root (with its parent /run mounted underneath it in a twist), and from the initramfs init script where it copied the files from its root directory into the /run/initramfs directory for use at shutdown time when the original rootfs is no longer reachable. By looking under /run/initramfs we will always look at one copy of the whitelist. This will also allow future modes where the update script can be invoked while running from a copies of the file systems located in RAM. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Instead of in saving files in root which is messy and logically part of the cow space, save the files in a directory under /run which will be mounted during init, runtime, and shutdown. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
This will allow us to restore or check-point the whitelisted files to the read-write filesystem device without causing confusion by mounting over the upperdir location while at runtime. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
This will ensure the cp command always writes to an existing directory but will also make any future component directories if the upper directory is later moved from the root of the filesystem. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Use the full /run/initramfs/rw path for the mount point of the read-write filesystem. This prevents creating and directories in / when it is invoked before shutdown. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Skip mounting and unmounting the read-write file system when saving files if the upper directory exists. Instead interpret this as a sign the system either is or was running from RAM (or from some future alternative and maybe temporary mounted file system) and save the files from that upper directory. It is possible some other filesystem is mounted on the read-write mountpoint that is not a mtd device, either a tmpfs or some other future media, so only try to unmount the file system if this update script mounted it. Each boot an empty /run filesytem is created and populated by init with selected directories and mount points for the read-only and read-write file systems and mounts them on these points. The upper directory is under the read-write mount point, so if it exists then either a file system is mounted there or the system was prepared to run from RAM using the run tmpfs file system and updates may have been made there. In either case the files to be saved exist in that directory. Background on overlayfs: The upper directory contains files and directory entries that were either opened for write or had meta data changed. Before this happens the overlayfs copies each file or directory by name into the work directory then atomically moves it into the corresponding upper directory. To form a read-write overlayfs mount, the upper directory must be, by definition, in a read-write file system along with the work directory, and both are required to be in the same filesystem. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Add an option to copy files to the runtime copy-on-write upper directory from the saved directory to allow init to request the files for use without knowing the saved files directory. This will be used to initialize the cow directory from the persistent rwfs file system when choosing to run in RAM. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Remove image files as they are flashed so a repeated call to update does not erase and write the image again. As we add the ability to call update at runtime repeated calls are expected. This both signals successful copy and removes the need for callers to cleanup. Also remove commented alternate flash method using eraseall that was not tested. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Note explicitly when an empty image is provided that will not alter a flash partition. While using flashcp on an empty file succeeds and does not alter the flash, it may be confusing to see 0/0 messages for the erase, write, and verify phases. These empty files are used to trigger the save and restore phases and may also be used by developers to cause the update to fail and break into a shell at shutdown for maintence. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Grep options from a file instead of directly from /proc/cmdline which will allow additonal sources for options. Initially the options file is just a copy of the kernel command line, but it may be edited at debug-init-sh or via a later debug_takeover point or before restarting init. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
If a read-only file system image is in /run, specifically /run/image-rofs, then mount it instead of the mtd partition. This will allow running from ram to allow the flash to be updated, either from a downloaded image, a packaged image, or an image copied at boot. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Decide lack of fsck is not a problem by the type of the rwfs image instead of the full name of the fsck command. This eliminates duplicates knowledge of how the fsck path is formed. Suggested-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Allow file system type none for rwfst, which means do not mount a separate file system but just use the directory in the tmpfs /run. This will be used to allow the flash controller to not be used by the running image, allowing flash updates while the BMC is running the main application. It could also be used for a file system less prone to corruption where the read-write overlay is only updated with whitelisted files at specific points in time with updates to the update script. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
If images are to be updated before init continue to move them to /run/initramfs. However, if they are not to be flashed before init instead move them to /run. This will result in the image-rofs being loop mounted for this run, and all images will be available at runtime for flash update at runtime. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
If overlay-filesystem-in-ram is found set rwfst=none suppressing the rwfs mount. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
If copy-base-filesystem-to-ram is found copy the read-only filesystem source device to /run/image-rofs. If the copy fails then remove the partial copy and invoke debug takeover. This will allow a new image to be downloaded and flashed while running from the existing copy for the duration of this boot. Alternatively with the overlay also in RAM pflash could be used to update the flash from the host as the BMC would no longer need the flash or flash controller. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
When calling update for save and restore phases be explicitly tell update to clean saved files when we are done and not bother trying to save or restore when we know we will do a split save, erase, and restore sequence. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Use the copy in /run/initramfs/update to call update to be consistent with other uses. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Add an option to copy files from the rwfs to ram then run in ram. This allows customizations like user ids and network settings to be initialized from the read-write filesystem. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Look in the saved u-boot environment for init options in addition to the kernel command line. This allows setting options to run in the u-boot environment instead of setting bootargs. Look at specific variables but not the whole environment so that users can setup variable to run. Look at two variables so scripts can automatically clear one on successful boot as one-time options (defer that to the full filesystem). Instead of having the full fw_setenv / fw_getenv binaries which would overflow the existing space for the initramfs, just use the busybox strings command to extract the variables. The oldest variable might get a crc32 character or flag byte if redundant environment were configured for nand but that is not expected to be these user defined variables. [1] The environment consists of a crc32, a flag byte if a redundant environment is configured, then a series of var=value strings separated by NUL bytes. The flag byte is 1 (active) or 0 (obsolete) for NOR flash, or a counter 0-255 in nand, the flag byte cycles through 0-255. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
If the file /init-options exists copy it to the runtime location /run/initramfs/init-options. This allows an initramfs image to be built that will not parse any u-boot or command line variables by adding a file into the the image. This can be done either through a recipe overlay or additonal package today and could also be a cpio merged into the initrd in the future. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Add a hook to download a read-only file system image file from a URL using TFTP, HTTP, or FTP. The URL is retrieved from a u-boot environment variable unless the file is already in the initramfs image. Only execute this command if the previously established options file has a keyword trigger. Do not even consider the option if a build option flag is not set to y, and allow each protocol to be disabled by simiar build options. This allows one to specify at u-boot commands that would download a read-only file system into memory for execution this boot instead of needing to create a custom initramfs to netboot or specifying debug-init-sh, entering the password, and doing the download from the shell. Note: Access to set u-boot environment variables implys the ability to replace the kernel and initramfs session. Access to the variables and the serial console likely gives full root access to the system at this time. The existing shutdown and update scripts have paths that expose a root shell to the serial port without a prior password challenge. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Install the init-option and init-download-url if they exist in the build directory. This change to the bitbake recipe allows an override layer to simply add these files to the SRC_URI variable and then have them appear in the initramfs. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Create a service unit to clear the openbmconce variable in the the u-boot environment with fw_setenv. Set the timeout to allow the flash to be written, even though we currently just update the ram shadow file. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Tell systemd the host-ipmid service wants the clear-once service to be started, and that it wants to run after the clear-once service. The new OEM command will use the openbmc init run once variables set in the u-boot environment. We want the u-boot variable cleared before the host can request it be set again. Tell bitbake to require the clean-once package. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
Deleting a variable with a long value exposed a duplicate openbmcinitdownloadurl variable resulting in two lines in the url file, and wget was not happy. The u-boot environment ends with a double NUL character like many operating environments. Using strings to separate on the NUL bytes was loosing this information. The fw_printenv command does not clear the remainder of the environment when deleting variables. Instead it just makes sure it is terminated with a double NUL byte. Switch from strings to tr to separate the strings. Translate NL to CR to avoid false matches, and use sed to detect a blank line. Also use tail to skip over the CRC bytes. We don't have the config file to know if a flag exists so assume 1 copy for now. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
nkskjames
added a commit
that referenced
this pull request
Mar 8, 2016
Update openbmc initfs to add temporary run from RAM
stefanberger
pushed a commit
to stefanberger/openbmc
that referenced
this pull request
Aug 1, 2023
Sandeepa Singh (47): Firmware-change (openbmc#66) Allow only tar file upload (openbmc#71) Hardware Deconfiguration Page (openbmc#84) Deconfig-Toggles (openbmc#110) Filter SNMP data (openbmc#112) Upload acf certificate on login page (openbmc#126) Hardware deconfiguration fix (openbmc#128) TFTP firmware update (openbmc#104) Add filter to remove absent dimms form GUI (openbmc#139) Add abiliy to sort hardware deconfig columns (openbmc#162) Add helptext for FQDN (openbmc#164) Add deconfiguration type as None (openbmc#163) Fix link to deconfiguration records (openbmc#155) Remove regex from firmware (openbmc#151) Add alert for HMC connection disconnect (openbmc#152) Update hardware deconfiguration per Demo feedback (openbmc#180) Remove Default option from Server power operations page (openbmc#188) reverting removal of Default partition environment dropdown (openbmc#190) Add Lateral cast out page (openbmc#177) fix toggle issue (openbmc#191) Add details on login page (openbmc#193) Remove TFTP server option from firmware page (openbmc#194) Real time post codes converted to ASCII (openbmc#207) fix TFTP bug (openbmc#213) Show/Hide ACF upload button (openbmc#214) Fix toggle issue (openbmc#219) Change the toggle text to configure/deconfigure (openbmc#223) Fix the sorting issue in progress logs (openbmc#240) Translate severity to fatal,predictive and manual (openbmc#235) Add Pel ID column on HW deconfiguration page (openbmc#244) Show FW_boot_side_current attribute value (openbmc#262) Added filter to remove 00000000 from post code table (openbmc#272) Fix toast msg for HW deconfiguration page (openbmc#251) Add location code of Deconfig records page (openbmc#293) Make memory page consistent (openbmc#308) Add pel id column (openbmc#332) Update service login condition (openbmc#326) Edit app nav and login file (openbmc#335) Update Automatic helptext (openbmc#340) Grey out toggle when DHCP is disabled (openbmc#338) Disable delete when system is powered on (openbmc#327) Renamed added optimization page (openbmc#346) Fix deconfiguration record translation bug (openbmc#360) Fix power page translation bug (openbmc#361) Operating mode is translatable now (openbmc#363) Fix user management page translation bugs (openbmc#365) Fix server power ops translation bugs (openbmc#359) Kenneth Fullbright (85): Removed irrelevant fields from the VET Capabilities table (openbmc#68) Update Firmware page interactions when system is powered on (openbmc#51) Updated CSR Modal & Service login Certificate Modal (openbmc#59) Removed OemIBMServiceAgent from Group Privilege list (openbmc#76) Updated Power saver modes descriptions (openbmc#83) Popup SOL Console (Host Console) not showing correct connection status (openbmc#79) Removed irrelevant fields from the VET Capabilities table (openbmc#93) Added Initiate Resource Dump Function (openbmc#103) Fixed password change/reset code for expired password (openbmc#125) Fixed global action vuex error getUsers (openbmc#120) Fixed 'Promise.all' related errors on Overview (openbmc#119) Renamed "Serial over LAN (SOL) console" page (openbmc#54) Fixed event log table to be fully responsive (openbmc#122) Prevent service user password change (openbmc#88) Turned dumps PHYP alert into a toast (openbmc#140) Repaired Service login consoles links in the navbar (openbmc#145) Removed LDAP from navigation on non admin role accounts (openbmc#108) Updated the link to consoles and other nav related items Refactored Power page and power page related things (openbmc#109) Added Power restore policy missing alert on operating mode manual (openbmc#147) Made non-service roles not pass default password for resource dumps (openbmc#135) Fixed BMC Hypervisor console switch (openbmc#159) Enhanced user creation and current user failed message for password change (openbmc#81) Fixed translation double key error (openbmc#146) Removed service privilege option from edit user and add user (openbmc#161) Enhanced resource dump error messages (openbmc#168) Refactored Power page code for efficiency and clarity (openbmc#158) Fixed init system dump from resource dump (openbmc#136) Added toast for invalid privilege (openbmc#172) Fixed Service consoles (openbmc#176) Fix user management delete table action (openbmc#179) Fixed service account resource dumps password field to allow any string (openbmc#183) Fixed Idle power saving missing reset button option (openbmc#184) Removed lower and upper limit and warning sensors (openbmc#186) Fixed missing fields for add user on user modal (openbmc#185) Fixed maximum amount of users toast error (openbmc#196) Fixed delete and replace function in Certificates table (openbmc#197) Fixed navbar missing error (openbmc#206) Fixed popup BMC and Hypervisor consoles. (openbmc#205) Fixed init system dump PHYP in standby check error (openbmc#204) Fixed closing console conntections. (openbmc#220) Fixed upload certificate button not being disabled on max certificates (openbmc#224) Added info tool tips on password changing fields. (openbmc#225) Removed operator role from add role group modal (openbmc#229) [SW550540] Removed Operator and NoAccess roles from desciption table (openbmc#228) [SW550558] Fixed proxy logout error (openbmc#226) Created info icon for enhanced information about power consumption (openbmc#232) Fixed some tables not being fully responsive (openbmc#222) Set autocomplete option to off for password fields (openbmc#231) Added dump being offloaded warning for reboot and shutdown (openbmc#241) Fixed system dump error messages (openbmc#238) Fixed factory reset to default code (openbmc#243) Changed OemIBMServiceAgent to ServiceAgent (openbmc#261) Add safe mode to user interface (openbmc#250) Fixed fresh install set password and login error (openbmc#263) Fixed DHCP delete button not disabled (openbmc#273) Removed unsupported ServiceAgent group from LDAP group privilege modal (openbmc#268) Fixed Zombie state when factory resetting (openbmc#270) Fixed unauthorized error toast on page loading (openbmc#267) Fixed firmware swapping confusion (openbmc#271) Fixed console connection indicators (openbmc#275) Fixed account polocy settings displaying not updated info on refresh (openbmc#276) Fixed running and backup image info render problem (openbmc#287) Fixed event logs not updating upon delete all button (openbmc#290) Fixed account policy radio buttons (openbmc#289) Fixed secure LDAP checkbox not showing correct values (openbmc#291) Fixed firmware update function (openbmc#296) Fixed JSON.parse error from localStorage (openbmc#298) Fixed factory reset function to be fully async (openbmc#306) Removed host console access from ReadOnly roles (openbmc#307) Fixed SRC Details not showing on non manual records (openbmc#300) Fixed page memory validation error (openbmc#313) Fixed location code not showing on Deconfiguration records table (openbmc#317) Disabled users from changing username on user management table (openbmc#321) Added Location codes for TPM (openbmc#324) Fixed console indicators not updating status (openbmc#304) Added Location codes for TPM (openbmc#325) Made more meaningful toasts (openbmc#314) Fixed manage access keys hyperlink being disabled problems on Firmware page (openbmc#322) Fixed asset tag info not showing up in modal after app refresh and tag update (openbmc#333) Removed hashes from files (openbmc#334) Created real time indicator postCodeValue filter (openbmc#302) Fixed Deconfig table download additional data button (openbmc#328) Changed page "Lateral cast out" to "Added optimization" (openbmc#341) Added notices page (openbmc#336) A Nikhil (47): Update Inventory DIMM table (openbmc#74) Update Inventory Assemblies table (openbmc#87) Update Inventory Processors table (openbmc#86) Incorrect Power mode value (openbmc#89) Dumps available on BMC are not displayed on BMC-GUI (openbmc#72) Components on the hardware page not in order (openbmc#101) No values populated for licensed and configured cores (openbmc#91) Update GUI as IBM (openbmc#116) Rename Update Firmware access key (openbmc#117) Health and state field of assembly components is missing in inventory page (openbmc#99) Event logs add missing information (openbmc#111) GUI has no way to turn off System attention LED (openbmc#129) Event log does not show information for service (openbmc#133) GUI missing detailed COD (openbmc#124) Rename count in system table (openbmc#149) FCO page accepts value greater than the number of licensed cores (openbmc#142) Part number field is showing spare part number value (openbmc#165) Wrong lable on SRC for logs (openbmc#156) Inventory and LEDs page has two system entries (openbmc#137) Add toggle to enable/disable the secure version lock in (openbmc#167) Factory reset option should only be provided at power off (openbmc#174) Health in critical state after marking critical errors as resolved (openbmc#189) Concurrent maintenance Page (openbmc#202) Download implementation in Event logs (openbmc#192) Missing host USB enable/disable (openbmc#239) Prevent system power on when BMC is not in Ready state (openbmc#227) Adding mex chassis Info (openbmc#233) Mex IO enclosure firmware version not displayed (openbmc#265) PCIe Hardware Topology (openbmc#181) Warning in PcieTopology.vue (openbmc#282) Pcie-topology and Inventory fixes (openbmc#288) Unable to edit group name in the Add Role group field. (openbmc#303) PCIe Topology Save changes (openbmc#309) Invalid range for I/O Adapter enlarged capacity (openbmc#311) Status for both system and chassis comes as absent at host power off state (openbmc#312) Status for system table should be Present (openbmc#320) Fixed Identify LED error in MEX chassis (openbmc#330) Assemblies section does not has search option in Inventory page (openbmc#315) PCIe link width for empty slots is showing as -1 (openbmc#319) Warning message only in manual mode (openbmc#323) Fixed incorrect Identity LEDs error message (openbmc#331) Unwanted fields for MEX components removed (openbmc#329) PCIe topology performance improved (openbmc#337) AIX/LINUX and IBM i partition are only for non-HMC manage system (openbmc#318) Severity values is now translatable (openbmc#357) Enabled value taken from translation file (openbmc#362) Removed .tar.xz extension from dumps (openbmc#410) whitesource-ets[bot] (1): Add .whitesource configuration file sandeepasingh116 (17): Add new toggles on CM page (openbmc#3) Changed connection status logic for Hypervisor console (openbmc#6) Remove dump download option from overview page (openbmc#9) Add text on user management page (openbmc#8) Rename the save setting button (openbmc#20) Add success toast (openbmc#18) Fix network eth1 error (openbmc#21) Disable date and time page (openbmc#24) Update password helptext (openbmc#19) Add info tooltip to frequency cap (openbmc#25) Read only user will not be able to toggle switches (openbmc#28) Make filters translatable (openbmc#33) Fix translations of vet capabilities (openbmc#35) fix english texts containing links (openbmc#38) Remove service login label for read only user (openbmc#45) fix translation defect for server power ops (openbmc#52) add toogle on Policies page (openbmc#73) Reed Frandsen (1): Removed alert message from Update firmware component (openbmc#90) Gunnar Mills (3): Enable hmc proxy (openbmc#208) Update notices to 1030 (openbmc#50) Revert "Refresh only once after login (openbmc#42)" (openbmc#59) Nikhil Ashoka (33): pdated the text of server power ops documentation (openbmc#7) Displaying Sensors table one row at a time (openbmc#11) NTP server duplicate entry is not accepted (openbmc#4) Fabric Adapters Info in Inventory page (openbmc#12) Fixed Secure LDAP using SSL checkbox value (openbmc#2) Added progress bar for activate access key (openbmc#1) Error message displayed if fails to authenticate the user (openbmc#10) Memory page made HMC-managed independent (openbmc#15) Sorting fixed for status (openbmc#17) Sensors table now updating on refresh (openbmc#22) Secure LDAP is disabled when LDAP authentication disables (openbmc#23) Removed Service consoles page for read-only users (openbmc#14) Additional message added on Disable SSH (openbmc#30) Default partition value taken from translation file (openbmc#36) Updated password Max Limit (openbmc#26) New Error message displayed if fails to authenticate the user (openbmc#27) Added Status and roles values to the translation file (openbmc#31) Title translation (openbmc#34) Power values added to translation file (openbmc#32) Health and Date format taken from translation file (openbmc#37) Added possible property values in translation file (openbmc#39) Displaying System Anchor value (openbmc#40) Added Info tooltip to VirtualTPM (openbmc#47) Added max limit based on selected user (openbmc#46) Refresh only once after login (openbmc#42) Lamp test switch disabled once ON (openbmc#48) Tab names translated in Inventory page (openbmc#54) Using privilege values from the translation file (openbmc#56) Deconfiguration type is taken from translation file (openbmc#57) Fabric Adapter table showing Name (openbmc#55) PCIe topology overlapping fix (openbmc#53) Added Identity LED to Fabric Adapters (openbmc#49) Removed Error message from Accounts verification (openbmc#44) Dixsie Wolmers (14): Fix network settings defects - FQDN, link info, and MAC address (openbmc#113) Audit translation file (openbmc#115) Network settings - update DHCP section (openbmc#114) Add deconfiguration logs page (openbmc#121) Fix host console route (openbmc#157) Fix language dropdown on login page (openbmc#166) Network settings fixes - dhcp modal, edit ipv4, default gateway (openbmc#175) Update deconfig log table (openbmc#200) Update network settings ipv4 table (openbmc#199) Fix network settings hostname and IUM errors (openbmc#210) Add ability to edit asset tag (openbmc#211) Fix LDAP form values when LDAP disabled - SW546990 (openbmc#245) Fix deconfig records defects (openbmc#246) Update maintainers - Remove Dixsie and add Sandeepa (openbmc#286) aixt9n aixt9n (2): i18n: KO_KR: Drop latest translated files for webui-vue (openbmc#257) i18n: ES_ES: Drop latest translated files for webui-vue (openbmc#258) Change-Id: Ib5cb6cfccace5b718d22173ff1df4e8ce2a1e05c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This series adds support to the openbmc phosphor initfs scripts to support the BMC running with either or both of the read-write and read-only layers of the root file system to be in RAM instead of in the flash.
This decision is made via u-boot firmware variables and the kernel command line, and is designed to have a persistent and one time option.
Also included is a systemd service called clear-once that clears the variable meant for one time use. The host-ipmid service is modified to want to run after the clear-once service in anticipation of the a OEM command that will set the variable.
When running in RAM the read-write layer can be replaced with updated content. If both layers are in memory the BMC will not be accessing the flash except by explicit action, which include a shutdown and reboot.
This series includes support to copy the read-only layer from the existing flash at boot, and to copy the white listed files from the read-write file system at boot and restore them at shutdown along with the u-boot environment. Also included is support for using images sourced from elsewhere either by manual intervention at the debug-init-sh shell prompt or via a shell command line stored in a u-boot environment variable (only executed if an option is found on the command line or in the previously mentioned u-boot variables). This can be used to download the read-only layer from the network to test or run a new read-only layer while updating the flash. The packaged initfs supports HTTP ant TFTP transfers via the busybox commands.
The updated flash update script can run while the BMC is at system runtime if both layers are in RAM. Future updates will allow it to update one layer while the other is mounted. The error handling in the update script still is designed for use at shutdown with a console to debug and fix unexpected conditions. Future updates could also support leaving the watchdog timer enabled during flash, but a reset during an update to u-boot will always be fatal without a redundant flash chip and the corresponding strapping and support.
The options and variable names were listed in this prior email https://lists.ozlabs.org/pipermail/openbmc/2016-March/002119.html
. Documentation for this and network booting will be written.