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.

Sign up for GitHub

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
Merged

Document network support for configdrive #412

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source/adminguide/api.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,7 @@ VMdata - a list of String arrays representing [“directory”, “filename”,

- meta_data.json

- Network_data.json
- network_data.json

- label, which is configurable in global settings:

Expand Down
13 changes: 10 additions & 3 deletions source/adminguide/networking/dns_and_dhcp.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,13 @@
DNS and DHCP
------------

The Virtual Router provides DNS and DHCP services to the guests. It
proxies DNS requests to the DNS server configured on the Availability
Zone.
The Virtual Router & ConfigDrive (since Apache CloudStack 4.20) provides
DNS and DHCP services to the guests. It proxies DNS requests to the DNS
server configured on the Availability Zone.

.. 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

@weizhouapache weizhouapache Jul 10, 2024

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

@vishesh92 vishesh92 Jul 10, 2024

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

@vishesh92 vishesh92 Jul 10, 2024

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

@vladimirpetrov vladimirpetrov Aug 5, 2024

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).

`cloud-init clean --machine-id -s` to clean the machine id and seed data.
Then reboot the instance to apply the changes.
15 changes: 15 additions & 0 deletions source/adminguide/templates/_cloud_init.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,6 +215,21 @@ These features can be implemented in `“Linux Template creation process” <_cr

Cloud-init can parse and execute user-data form Cloud-stack during Instance creation. This feature works as is without additional configuration.

#. **Network configuration with ConfigDrive**

Cloud-init can fetch network configuration from ConfigDrive. To enable this,
ensure network configuration is not disabled in cloud-init configuration.

.. code:: bash

echo -e "\nnetwork: {}" >> /etc/cloud/cloud.cfg

.. note::
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 `cloud-init clean --machine-id -s` to clean the machine id and
seed data. Then reboot the instance to apply the changes.

#. **Cleanup**

Once desired cloud-init features are implemented, clean cloud-init tracker files.
Expand Down