WALinuxAgent | Microsoft Azure Linux Guest Agent | Azure library

by Azure Python Version: pre-v2.9.1.1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | WALinuxAgent Summary

WALinuxAgent is a Python library typically used in Cloud, Azure applications. WALinuxAgent has build file available, it has a Permissive License and it has low support. However WALinuxAgent has 4 bugs and it has 3 vulnerabilities. You can download it from GitHub.

Microsoft Azure Linux Guest Agent

Support

Quality

Security

License

Reuse

Support

WALinuxAgent has a low active ecosystem.

It has 498 star(s) with 378 fork(s). There are 91 watchers for this library.

There were 1 major release(s) in the last 12 months.

There are 62 open issues and 896 have been closed. On average issues are closed in 87 days. There are 17 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of WALinuxAgent is pre-v2.9.1.1

Quality

WALinuxAgent has 4 bugs (0 blocker, 0 critical, 1 major, 3 minor) and 755 code smells.

Security

WALinuxAgent has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

WALinuxAgent code analysis shows 3 unresolved vulnerabilities (3 blocker, 0 critical, 0 major, 0 minor).

There are 202 security hotspots that need review.

License

WALinuxAgent is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

WALinuxAgent releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

WALinuxAgent saves you 17015 person hours of effort in developing the same functionality from scratch.

It has 33782 lines of code, 3098 functions and 226 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed WALinuxAgent and discovered the below as its top functions. This is intended to give you an instant insight into WALinuxAgent implemented functionality, and help decide if they suit your requirements.

Read the route table .
Return a list of data files .
This function creates a random number of event events and a number of bad events .
Make a HTTP request .
Run the latest agent .
Check the WA agent log for errors .
Returns an OSutil instance .
Collects the status of an extension .
Parse plugin settings .
Create a new file .

Get all kandi verified functions for this library.

WALinuxAgent Key Features

No Key Features are available at this moment for WALinuxAgent.

WALinuxAgent Examples and Code Snippets

No Code Snippets are available at this moment for WALinuxAgent.

Community Discussions

Trending Discussions on WALinuxAgent

/usr/local/ reset for custom centos7 image on azure scale set

QUESTION

/usr/local/ reset for custom centos7 image on azure scale set

Asked 2021-Oct-15 at 16:49

We're using Packer to construct a custom centos7 image for an Azure scale set. Part of this includes a custom rpm that we have created that builds git from source (can't use community repos so we make our own) and installs it to the /usr/local/bin directory. In normal practice, the package works perfectly. Everything gets installed appropriately to the right places and we can use our new version of git.

When we run things through Packer, we install it via ansible, and then finally Packer does the deprovisioning step, captures the image and puts it in an azure shared image gallery, which we then pick up for use in our azure scale set.

Scale set uses the image to make a few instances, and we're up and running. Problem is, suddenly, the /usr/local/ directory seems to be as if it has been reset to default. There's nothing in /usr/local/bin anymore, and furthermore, some (not all) of the packages that we install as dependencies to build git (like gcc for example), also just disappear. Our git rpm is still listed as installed, but gcc is not.

/usr/bin/ seems fine (aside from the missing gcc, and though we don't need it at this point anyway, it still seems concerning), so we can probably just install it there, but I'd still like to know if something crazy is happening, and should I look out for it in the future seeing as /usr/local/ seemed a logical spot to install it.

TL;DR:

packer gets base centos7 image
add our custom git package
git installs to /usr/local/bin (it works! git is available)
deprovision with waagent and generalized
packer captures image and uploads it
azure scale set uses image to make new instances
/usr/local/ is back to original state? (thus git is missing?)
???

packer azure arm docs

waagent deprovisioning tool docs

...

ANSWER

Answered 2021-Oct-15 at 16:49

Figured this out.

Turns out (at least with version 1.7.2) Packer does not necessarily do idempotent operations with the azure arm in relation to Shared Image Gallery versions, even with the --force flag.

We had created the SIG image version before we had gotten our git package fully working and installed properly, so it was created on a base image that did not have /usr/local/bin/ modified.

When we ran the Packer build with the force flag, it deletes and recreates the base image, but it runs a PUT call with the configuration information for the SIG image version, which is to say it will "Create or Update" if it's following convention (you can't see this unless you set some packer logging vars and output the verbose logs to a file or something).

So while the base image was updated to one that had git properly set up, the SIG version thought it was using the same base image as before (the name was the same, no unique identifier), so as far as it was concerned the configuration hadn't changed and nothing needed to happen. After we deleted the old version or made a new version, it properly spun up a VM based on the base image we had made and everything was where it was supposed to be.

I am definitely of the opinion that a --force should be an idempotent operation from start to finish, I'm not sure if this is fixed in future versions (at the time of writing this they're on 1.7.6) but maybe I'll update once I've checked it out.

Source https://stackoverflow.com/questions/69561820

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install WALinuxAgent

Installation via your distribution's package repository is preferred. You can also customize your own RPM or DEB packages using the configuration samples provided (see deb and rpm sections below).
Upgrading via your distribution's package repository is strongly preferred.

Support

Our daily automation tests most of the Linux distributions supported by Azure; the Agent can be used on other distributions as well, but development, testing and support for those are done by the open source community. Testing is done using the develop branch, which can be unstable. For a stable build please use the master branch instead.

Find more information at: