** Description changed:

  [Availability]
  The package azure-vm-utils is already in Ubuntu universe.
  The package azure-vm-utils build for the architectures it is designed to work 
on.
  It currently builds and works for architectures:  
amd64,arm64,armhf,ppc64el,riscv64,s390x
  Link to package https://launchpad.net/ubuntu/+source/azure-vm-utils
  PPA for the proposed package: 
https://launchpad.net/~mirespace/+archive/ubuntu/azure/+packages
                                
https://launchpad.net/~mirespace/+archive/ubuntu/azure/+sourcepub/16868631/+listing-archive-extra
  
  [Rationale]
  The package azure-vm-utils is required in Ubuntu main for enhacing the 
experience of the users of our Azure images using NVMe devices nowadays: this 
package provides a home for core utilities, udev rules and other  configuration 
to support Linux VMs on Azure.
  The package azure-vm-utils will not generally be useful for a large part of 
our user base, but is important/helpful still because the users of our Azure 
images will have in this package any essential udev rules & relevant utilities.
  Package azure-vm-utils covers the same use case as walinuxagent for SCSI 
devices, but there is a plan in the near future to decouple that from 
walinuxagent [1]. Therefore,
  we want to be ready for when that transition occurs to prevent the impact in 
our users.
  Additionally new use-cases enabled by this are the automatic support of NVMe 
devices in Azure images.
  Aditional reasons are that users who only need the dev rules don't need the 
heavy load of the agent and can get that throught this light azure-vm-utils 
package.
  There is no other/better way to solve this that is already in main or should 
go universe->main instead of this.
  The binary package azure-vm-utils needs to be in main to be available in our 
official Azure cloud images by default.
  
  The package azure-vm-utils is required in Ubuntu main no later than this
  cycle (target is release of 25.04) due to the transistion of the udev
  rules from walinuxagent to vm-azure-utils.
  
  [Security]
  No CVEs/security issues in this software in the past
  No `suid` or `sgid` binaries
  Binary azure-nvme in /usr/sbin is no problem because it is not suid/sgid; it 
as query tool over the NVME namespace to enumerate Microsoft Azure NVMe 
controllers that could be executed in command line and from the udev rules file 
that the package installs.
  Package does not install services, timers or recurring jobs
  Security has been kept in mind and common isolation/risk-mitigation patterns 
are in place by the security of Windows Azure Cloud (Iaas) itself, being 
tangential to it.
  Packages does not open privileged ports (ports < 1024).
  Package does not expose any external endpoints, althought it elaborates LUN 
calculation for user's data disks by namespace identifier throught the MSFT 
NVMe Accelerator v1.0 controllers when the NMVe device is remote. This is done 
in the udev rules file installed by the package.
  Packages does not contain extensions to security-sensitive software (filters, 
scanners, plugins, UI skins, ...)
  
  [Quality assurance - function/usage]
  The package works well right after install
  
  [Quality assurance - maintenance]
  
  The package is maintained well in Debian/Ubuntu/Upstream and does
  not have too many, long-term & critical, open bugs (also beacuse it was 
accepted in Debian recently -Oct 12, 2024- and first released version
  in upstream happened in Feb 12, 2024):
  - Ubuntu (0) https://bugs.launchpad.net/ubuntu/+source/azure-vm-utils/+bug
  - Debian (0) https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=azure-vm-utils
  - Upstream's bug tracker (1) https://github.com/Azure/azure-vm-utils/issues
     + Upstream's repo last activity:
         - last commit: in main, Nov 26, 2024
         - Issues without answer: 1
         - Updated issue/PR: Dec 10, 2024
         - last fixed/closed/merged issue: Nov 26, 2024
         - last merged PR: Mar 30, 2015
  The package has not important/old open bugs on upstream.
  The package does deal with exotic hardware, such hardware is available to the 
team for debugging, test, verification and development via Azure cloud providers
  
  [Quality assurance - testing]
  - The package does not run a test at build time
  - The package does not run an autopkgtest, but the proposed package include a 
trivial one based un upstream's github CI for the deb package [2]. It passes:
  
      autopkgtest [13:00:04]: test installation: [-----------------------
      Checking files provided by the package are present
      Checking binary is present and its usefulness
      azure-nvme-id 0.4.0-2
      autopkgtest [13:00:05]: test installation: -----------------------]
      autopkgtest [13:00:06]: test installation:  - - - - - - - - - - results - 
- - - - - - - - -
      installation         PASS (superficial)
      autopkgtest [13:00:06]: @@@@@@@@@@@@@@@@@@@@ summary
      installation         PASS (superficial)
  
    Non-trivial autopackage tests should require configuring an Azure VM 
machine with specific storage to test
    the particular device this package support, and nowadays it only can be 
done manually with this plan:
  
     · the automated testing that the CPC team normally runs against Azure 
images before they are published will be run against the -proposed package
     · Installing the package in an Azure VM with NVMe storage (configure that 
kind of machine in advance) and checking that the created symlinks for the 
devices are as expected by the udev rules file intention.
     · CPC commits to do it in every release of the package or at least once 
each release cycle.
  
  - The package can not be well tested at build or autopkgtest time
  because infraestructure issues . To make up for that we have access to
  such hardware in  the team through the Azure portal to test our produced
  images with the manual plan proposed in the  point above. Although this
  is not ideal, we'll continue working to find an automated solution
  together, even upstream.
  
  [Quality assurance - packaging]
  - debian/watch is present and works
  - debian/control defines a correct Maintainer field
  
  - This package does not yield massive lintian Warnings, Errors
   - Recent build log of the package:
     - for sync package form Debian,amd64: 
https://launchpadlibrarian.net/756822028/buildlog_ubuntu-plucky-amd64.azure-vm-utils_0.4.0-2_BUILDING.txt.gz
     - for proposed package in ppa:mirespace/azure , amd64: 
https://launchpadlibrarian.net/770472873/buildlog_ubuntu-plucky-amd64.azure-vm-utils_0.4.0-2ubuntu1_BUILDING.txt.gz
  
   - full output from  `lintian --pedantic`:
     ❯ lintian -EvIL +pedantic --show-overrides
        W: azure-vm-utils source: newer-standards-version 4.7.0 (current is 
4.6.2)
        I: azure-vm-utils source: adopted-extended-field (in section for 
source) XSBC-Original-Maintainer [debian/control:5]
        I: azure-vm-utils source: quilt-patch-missing-description 
[debian/patches/fix-nonreproducible-manpage.patch]
        I: azure-vm-utils source: superficial-tests [debian/tests/control]
        X: azure-vm-utils source: debian-watch-does-not-check-openpgp-signature 
[debian/watch]
  - Lintian overrides are not present
  
  - This package does not rely on obsolete or about to be demoted packages.
  - This package has no python2 or GTK2 dependencies
  
- - The package will be installed by default, but does not ask debconf
- questions higher than medium
+ - The package will be installed by default in the Azure images, but does
+ not ask debconf questions higher than medium
  
  - Packaging and build is easy, link to debian/rules :
  https://git.launchpad.net/ubuntu/+source/azure-vm-
  utils/tree/debian/rules
  
  [UI standards]
  - Application is not end-user facing (does not need translation)
  
  [Dependencies]
  - No further depends or recommends dependencies that are not yet in main
  
  [Standards compliance]
  - This package correctly follows FHS and Debian Policy
  
  [Maintenance/Owner]
  The owning team will be CPC and I have their acknowledgement for that 
commitment
  The future owning team is not yet subscribed, but will subscribe to the 
package before promotion
  
  - This does not use static builds
  - This does not use vendored code
  - This package is not rust based
  
  - The package has been built within the last 3 months as part of a test 
rebuild : 
https://launchpad.net/ubuntu/+archive/test-rebuild-20241218-plucky/+sourcepub/16735656/+listing-archive-extra
  - The package has been built within the last 3 months in PPA : 
https://launchpad.net/~mirespace/+archive/ubuntu/azure/+sourcepub/16868631/+listing-archive-extra
  - Build link on launchpad: 
https://launchpad.net/ubuntu/+source/azure-vm-utils/0.4.0-2
  
  [Background information]
  The Package description explains the package well
  Upstream Name is azure-vm-utils
  Link to upstream project  https://github.com/Azure/azure-vm-utils
  
  As explained in the Rationale section, this package will be the future 
standard Core utilities and configuration for Linux VMs on Azure, detaching this
  functionality from walinuxagent/waagent, so we are addressing this change in 
the Azure ecosystem to prevent an unwanted impact on our uses.
  
  First time of publication in the Archive: 2024-10-31
  
  [1] https://github.com/Azure/azure-vm-utils/pull/40#issuecomment-2319179645
  [2] 
https://github.com/Azure/azure-vm-utils/blob/eed34b3f0aaee9a041c10b50161fb265b166bc7f/.github/workflows/debs.yml#L40

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2093322

Title:
  [MIR] azure-vm-utils

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/azure-vm-utils/+bug/2093322/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to