Skip to content

Document network support for configdrive #412

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 1 commit into from
Aug 26, 2024

Conversation

vishesh92
Copy link
Member

@vishesh92 vishesh92 commented Jul 10, 2024

.. note::
In case of a network with ConfigDrive, adding/removing nic to/from an
instance or updating the ip address of a nic will not be reflected in the
instance if the instance is already running. To do so, run
Copy link
Member

Choose a reason for hiding this comment

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

@vishesh92
if the instance is stopped, will the ip address be updated when it is started ?

Copy link
Member Author

Choose a reason for hiding this comment

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

It won't as of now. Let me make it more specific here.

Copy link
Member Author

Choose a reason for hiding this comment

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

This is a limitation of ConfigDrive with cloud-init. It applies network configuration from ConfigDrive only during the first boot.

Copy link
Contributor

Choose a reason for hiding this comment

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

I was definitely able to see the changes when adding/removing NICs only by executing stop/start VM sequence (not restart).

Copy link
Contributor

@harikrishna-patnala harikrishna-patnala left a comment

Choose a reason for hiding this comment

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

Question (asked the same on the PR also), how this needs to be configured in the network offering ? like we choose the config drive as the provider for userdata while creating the network offering. Or we don't need to ??

@harikrishna-patnala
Copy link
Contributor

@blueorangutan docbuild

@blueorangutan
Copy link

@harikrishna-patnala a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress.

@blueorangutan
Copy link

QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/412. (QA-JID 238)

@vishesh92
Copy link
Member Author

Question (asked the same on the PR also), how this needs to be configured in the network offering ? like we choose the config drive as the provider for userdata while creating the network offering. Or we don't need to ??

Yes. It's part of the network offering. Earlier, ConfigDrive wasn't available as an option for DHCP & DNS. Now it is.
image

image

Copy link
Contributor

@harikrishna-patnala harikrishna-patnala left a comment

Choose a reason for hiding this comment

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

doc LGTM

@harikrishna-patnala harikrishna-patnala added this to the 4.20 milestone Jul 15, 2024
@rohityadavcloud rohityadavcloud marked this pull request as ready for review August 5, 2024 08:18
@vishesh92 vishesh92 force-pushed the configdrive-network-support branch from b9fbd2d to 6b3b522 Compare August 12, 2024 19:13
@DaanHoogland DaanHoogland merged commit 38ef7e7 into apache:main Aug 26, 2024
1 check passed
@DaanHoogland DaanHoogland deleted the configdrive-network-support branch August 26, 2024 08:56
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.

6 participants