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

Removing ability to invoke walinuxagent from cloud-init #799

Merged
merged 6 commits into from
Apr 13, 2021

Conversation

anhvoms
Copy link
Contributor

@anhvoms anhvoms commented Feb 2, 2021

Proposed Commit Message

azure: removing ability to invoke walinuxagent from within cloud-init as this is no longer supported/necessary.

Additional Context

Test Steps

Checklist:

  • My code follows the process laid out in the documentation
  • I have updated or added any unit tests accordingly
  • I have updated or added any documentation accordingly

@anhvoms anhvoms changed the title Anhvo/remove wa linux agent shim Removing ability to invoke walinuxagent from cloud-init Feb 2, 2021
Copy link
Member

@TheRealFalcon TheRealFalcon left a comment

Choose a reason for hiding this comment

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

Overall this looks good. Is there a reason we can't also remove the other agent references? In DataSourceAzure.py, I'm looking at lines:
51,52,258,1254-1255

Should we still be defaulting data_dir to the AGENT_SEED_DIR (259)?
Is 'x-ms-agent-name': 'WALinuxAgent', still a valid header in azure.py (348)?
I still see a ton of waagent references in test_azure.py. Are all of those still valid?

We should also update doc/rtd/topics/datasources/azure.rst accordingly.

@github-actions
Copy link

Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close.

If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging mitechie, and he will ensure that someone takes a look soon.

(If the pull request is closed and you would like to continue working on it, please do tag mitechie to reopen it.)

@github-actions github-actions bot added the stale-pr Pull request is stale; will be auto-closed soon label Feb 26, 2021
@github-actions github-actions bot closed this Mar 5, 2021
@OddBloke OddBloke reopened this Mar 29, 2021
@OddBloke OddBloke removed the stale-pr Pull request is stale; will be auto-closed soon label Mar 29, 2021
@github-actions
Copy link

Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close.

If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging mitechie, and he will ensure that someone takes a look soon.

(If the pull request is closed and you would like to continue working on it, please do tag mitechie to reopen it.)

@github-actions github-actions bot added the stale-pr Pull request is stale; will be auto-closed soon label Apr 13, 2021
@anhvoms
Copy link
Contributor Author

anhvoms commented Apr 13, 2021

Overall this looks good. Is there a reason we can't also remove the other agent references? In DataSourceAzure.py, I'm looking at lines:
51,52,258,1254-1255

Should we still be defaulting data_dir to the AGENT_SEED_DIR (259)?
Is 'x-ms-agent-name': 'WALinuxAgent', still a valid header in azure.py (348)?
I still see a ton of waagent references in test_azure.py. Are all of those still valid?

We should also update doc/rtd/topics/datasources/azure.rst accordingly.

@TheRealFalcon
Re:data_dir: while we're removing the ability to invoke waagent from within cloud-init, waagent still manages extension handling for the VM and still depends on some artifacts from cloud-init. The data_dir is where the cloud-init caches the ovf-env.xml file in case of reboot during provisioning process. Waagent will also look into this directory for this file to know that cloud-init has proceeded to a certain stage of provisioning.
The header is still valid (some analyzers in the backend still look for this header)
The references in the test_azure.py are also valid

I will update the doc in azure.rst

@anhvoms anhvoms closed this Apr 13, 2021
@mitechie mitechie removed the stale-pr Pull request is stale; will be auto-closed soon label Apr 13, 2021
@anhvoms anhvoms reopened this Apr 13, 2021
Copy link
Member

@TheRealFalcon TheRealFalcon left a comment

Choose a reason for hiding this comment

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

Thanks @anhvoms , this looks good.

@TheRealFalcon TheRealFalcon merged commit 9f9e154 into canonical:master Apr 13, 2021
cjp256 added a commit to cjp256/cloud-init that referenced this pull request Nov 24, 2021
Some references were missed in the removal of the agent command
in PR canonical#799.  This simply removes the remaining references.

Signed-off-by: Chris Patterson <cpatterson@microsoft.com>
TheRealFalcon pushed a commit that referenced this pull request Nov 29, 2021
Some references were missed in the removal of the agent command
in PR #799.  This simply removes the remaining references.

Signed-off-by: Chris Patterson <cpatterson@microsoft.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

Successfully merging this pull request may close these issues.

None yet

4 participants