Skip to content
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

FTP server documentation needs update #96

Closed
jacobemery opened this issue Feb 8, 2023 · 0 comments
Closed

FTP server documentation needs update #96

jacobemery opened this issue Feb 8, 2023 · 0 comments

Comments

@jacobemery
Copy link
Collaborator

Now that the KVM host serves everything the bastion needs to boot via HTTP, the FTP server and its variables need to be updated to reflect that.

An FTP server is still required when the user is booting the KVM host(s) for the first time, but after that it is not required.

I haven't figured out yet how to differentiate / describe these two functions in all.yaml and the documentation.

jacobemery added a commit that referenced this issue Feb 23, 2023
Related to Issue #96 

The name 'FTP server' is confusing since the KVM host is now capable of
hosting and serving necessary files via http only. Update the docs and
variables to represent this change.

Also, enable using either ftp or http to serve config files for the
bastion. FTP is still the only option for booting the KVM hosts, as that
is the only option for the HMC to network boot from. And HTTP will still
be installed and used on the bastion as it is required. But with these
changes, someone using a pre-existing KVM host and NAT-based networking
can use only HTTP if they'd like. And someone using an FTP server for
booting of the KVM host(s) can use that same FTP server to boot the
bastion.

---------

Signed-off-by: Jacob Emery <jacob.emery@ibm.com>
jacobemery added a commit that referenced this issue Dec 20, 2023
Related to Issue #96 

The name 'FTP server' is confusing since the KVM host is now capable of
hosting and serving necessary files via http only. Update the docs and
variables to represent this change.

Also, enable using either ftp or http to serve config files for the
bastion. FTP is still the only option for booting the KVM hosts, as that
is the only option for the HMC to network boot from. And HTTP will still
be installed and used on the bastion as it is required. But with these
changes, someone using a pre-existing KVM host and NAT-based networking
can use only HTTP if they'd like. And someone using an FTP server for
booting of the KVM host(s) can use that same FTP server to boot the
bastion.

---------

Signed-off-by: Jacob Emery <jacob.emery@ibm.com>
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

No branches or pull requests

1 participant