Skip to content

feat: support for unattended zFCP configuration #2551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 18 commits into from
Jul 16, 2025
Merged

Conversation

jreidinger
Copy link
Contributor

@jreidinger jreidinger commented Jul 10, 2025

Problem

There is missing support to activate zFCP devices in unattended agama.

Solution

Implement it and also together with it fix also wrong dasd export at https://bugzilla.suse.com/show_bug.cgi?id=1246102

Testing

  • Added a new unit test
  • Tested manually

Manually tested with following profile ( first select product and then test it using agama config load. We cannot test it with full unatttended profile as our only s390 machine with zfcp available is already installed, so we tested it on installed system )

{
  "zfcp": {
    "devices": [
      {
        "channel": "0.0.fa00",
        "wwpn": "0x500507630b181216",
        "lun": "0x4020404900000000"
      }
    ]
  }
}

Documentation

related PR agama-project/agama-project.github.io#96

Ok(self.client.put_void("/storage/dasd/config", config).await?)
}

pub async fn supported(&self) -> Result<bool, DASDHTTPClientError> {
Ok(self.client.get("/storage/dasd/supported").await?)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps it might be good to have a /storage/supported or /storage/features that returns which features are actually supported in a single place. But I guess it is out of scope here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense for me, but I would do it in separate PR as it affects also web UI

pub async fn set_config(&self, config: &ZFCPConfig) -> Result<(), ZFCPHTTPClientError> {
if !self.supported().await? {
// TODO: should we add tracing error here?
return Ok(());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By now I would most probably add a warning.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question is if we should add tracing to agama-lib as currently it is only in agama-server and agama-network

@coveralls
Copy link

coveralls commented Jul 11, 2025

Coverage Status

coverage: 64.116% (-0.08%) from 64.199%
when pulling 066b230 on zfcp_unattended
into b75d0bd on master.

@jreidinger jreidinger marked this pull request as ready for review July 14, 2025 19:37
Copy link
Contributor

@imobachgs imobachgs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@imobachgs imobachgs changed the title Zfcp unattended feat: support for unattended zFCP configuration Jul 16, 2025
@jreidinger jreidinger merged commit f7bf908 into master Jul 16, 2025
30 checks passed
@jreidinger jreidinger deleted the zfcp_unattended branch July 16, 2025 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants