Some preparations for genesis_db reincarnation

[gmelikov]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces several foundational changes across documentation, configuration, and the data model. These updates are geared towards preparing the system for potential database re-initialization or significant infrastructure adjustments, ensuring proper data handling and system setup for a 'genesis_db reincarnation'.

Highlights

• Data Model Enhancement: Implemented a delete method for the NodeSet model in genesis_core/compute/dm/models.py to ensure that all associated Node objects are also deleted when a NodeSet is removed, preventing orphaned records.
• Configuration Update: Added a new resource_transformer named em_core_secret_passwords to etc/genesis_core/core_agent.conf, configured to ignore null attributes and process value attributes.
• Documentation Improvement: Updated docs/network/load_balancer.md to include detailed SSH requirements and setup instructions for external sources on Ubuntu 24, covering nginx, socat, and unprivileged port binding.

Changelog

• docs/network/load_balancer.md
  • Added a new section detailing SSH requirements for external sources, including installation commands for nginx and socat on Ubuntu 24, and configuration for unprivileged port binding.
• etc/genesis_core/core_agent.conf
  • Introduced a new resource_transformer entry for em_core_secret_passwords to handle sensitive data attributes.
• genesis_core/compute/dm/models.py
  • Implemented a delete method within the NodeSet class to ensure that when a NodeSet instance is deleted, all associated Node instances are also explicitly removed, preventing orphaned records.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces minor changes, including adding documentation for external SSH source requirements in the load balancer documentation and adding a delete method to the NodeSet class in the compute data model. I have added review comments regarding the potential security risk of including SSH private keys in the load balancer documentation and the good practice of cleaning up associated nodes when a NodeSet is removed.