Replace references to CBL-Mariner in documentation files with Azure l…

…inux as well as links (microsoft#8128)

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# CBL-Mariner's Contribution Guide
+# Azure Linux's Contribution Guide
 
 ## Table of Contents
 
@@ -63,20 +63,20 @@ Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https:
 
 <!-- END MICROSOFT SECURITY.MD BLOCK -->
 
-## Develop for CBL-Mariner
+## Develop for Azure Linux
 
-When starting to develop for CBL-Mariner, use the [CBL-MarinerTutorials](https://github.com/microsoft/CBL-MarinerTutorials) repo. This repository guides developers on using CBL-Mariner's tools to customize or add new packages or images. Once you have confirmed your change builds and functions as expected, consider whether it should be added to the core repo, [CBL-Mariner](https://github.com/microsoft/CBL-Mariner). Please see our [quickstart](toolkit/docs/quick_start/quickstart.md) for a tutorial and [building instructions](toolkit/docs/building/building.md) for an in-depth overview of building within CBL-Mariner. Please adhere to the [Pull Request guidelines](pull-request-guidelines) when contributing.
+When starting to develop for Azure Linux, use the [Azure LinuxTutorials](https://github.com/microsoft/AzureLinux-Tutorials) repo. This repository guides developers on using Azure Linux's tools to customize or add new packages or images. Once you have confirmed your change builds and functions as expected, consider whether it should be added to the core repo, [Azure Linux](https://github.com/microsoft/azurelinux). Please see our [quickstart](toolkit/docs/quick_start/quickstart.md) for a tutorial and [building instructions](toolkit/docs/building/building.md) for an in-depth overview of building within Azure Linux. Please adhere to the [Pull Request guidelines](pull-request-guidelines) when contributing.
 
 ### Packages
 
-CBL-Mariner packages live in either [SPECS](SPECS) or [SPECS-EXTENDED](SPECS-EXTENDED). CBL-Mariner packages that are in the `SPECS` directory have full support and coverage with timely CVE maintenance. Packages in `SPECS-EXTENDED` are for experimentation or proof-of-concept purposes only. `SPECS-EXTENDED` can be used as a staging area for iterating on packages with the possiblity of the package being graduated to `SPECS`.
+Azure Linux packages live in either [SPECS](SPECS) or [SPECS-EXTENDED](SPECS-EXTENDED). Azure Linux packages that are in the `SPECS` directory have full support and coverage with timely CVE maintenance. Packages in `SPECS-EXTENDED` are for experimentation or proof-of-concept purposes only. `SPECS-EXTENDED` can be used as a staging area for iterating on packages with the possiblity of the package being graduated to `SPECS`.
 
 | Package Support Level | Published | Supported | Comments
 |:----------------------|:----------|:--------|:------------
 |SPECS-EXTENDED         |**Yes**    |No       | - Package needs a viable upstream source which actively addresses CVEs </br> - Package must not include project specific code
 |SPECS                  |**Yes**    |**Yes**  | - Package needs a viable upstream source which actively addresses CVEs </br> - Package must not include project specific code </br> - Package needs to offer value for multiple use cases
 
-When looking to graduate a package from `SPECS-EXTENDED` to `SPECS`, file a [GitHub issue](https://github.com/microsoft/CBL-Mariner/issues) highlighting the package's value and ensure that the following steps are completed for associated PRs.
+When looking to graduate a package from `SPECS-EXTENDED` to `SPECS`, file a [GitHub issue](https://github.com/microsoft/azurelinux/issues) highlighting the package's value and ensure that the following steps are completed for associated PRs.
 
 1. Increment the spec's `Release` value
 1. Add changelog entries "Package promoted from SPECS-EXTENDED to SPECS" and "License verified"
@@ -87,7 +87,7 @@ When looking to graduate a package from `SPECS-EXTENDED` to `SPECS`, file a [Git
 
 ### Toolkit
 
-We welcome tooling improvements. When contributing to the toolkit, please adhere to `golang` formatting as described by the [fmt](https://pkg.go.dev/fmt) package. To format using this package, you can run `make go-tidy-all` in your CBL-Mariner toolkit. For guidance on building with the toolkit, see our [building instructions](toolkit/docs/building/building.md).
+We welcome tooling improvements. When contributing to the toolkit, please adhere to `golang` formatting as described by the [fmt](https://pkg.go.dev/fmt) package. To format using this package, you can run `make go-tidy-all` in your Azure Linux toolkit. For guidance on building with the toolkit, see our [building instructions](toolkit/docs/building/building.md).
 
 ### Documentation
 
@@ -151,11 +151,11 @@ When creating your PR, please ensure the following:
 
 * Any updated packages successfully build (or no packages were changed). For guidance on building packages, see our [building instructions](toolkit/docs/building/building.md). Please ensure the package is located in the [appropriate folder](#packages).
 
-* Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their `Release` tag incremented. Dependent packages are packages which contain a `BuildRequires` on the package you are updating and create static links from your package. This can be difficult to discern based on spec files alone and may require investigating `make` commands in dependent packages or consulting a CBL-Mariner dev.
+* Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their `Release` tag incremented. Dependent packages are packages which contain a `BuildRequires` on the package you are updating and create static links from your package. This can be difficult to discern based on spec files alone and may require investigating `make` commands in dependent packages or consulting an Azure Linux dev.
 
 * Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files. When running the check section, results will not fail a build. Check the logs for the results of this section.
 
-* All package sources are available. The sources are either in the source server or local `SPECS` folder (`SPECS/<package>/SOURCES` or `SPECS/<package>`). While it is possible to build packages with all sources inside the repo, our policy is generally to have the source compressed and placed on the source server. Uploading to the source server can only be accomplished by a CBL-Mariner developer. Please request help in your PR for uploading your sources to the source server. To check the source server see [https://cblmarinerstorage.blob.core.windows.net/sources/core/< source tar >].
+* All package sources are available. The sources are either in the source server or local `SPECS` folder (`SPECS/<package>/SOURCES` or `SPECS/<package>`). While it is possible to build packages with all sources inside the repo, our policy is generally to have the source compressed and placed on the source server. Uploading to the source server can only be accomplished by an Azure Linux developer. Please request help in your PR for uploading your sources to the source server. To check the source server see [https://cblmarinerstorage.blob.core.windows.net/sources/core/< source tar >].
 
 * cgmanifest files are up-to-date and alphabetically sorted. The cgmanifest files are used to record all package sources. They include the following files:
 
@@ -164,13 +164,13 @@ When creating your PR, please ensure the following:
   * ./toolkit/scripts/toolchain/cgmanifest.json,
   * .github/workflows/cgmanifest.json
 
-  To validate, run the following in a CBL-Mariner container or Ubuntu >= 22.04
+  To validate, run the following in an Azure Linux container or Ubuntu >= 22.04
 
   ```bash
   .github/workflows/validate-cg-manifest.sh SPECS/<package name>/<package-name>.spec
    ```
 
-* LICENSE-MAP files are up-to-date. These files indicate which licenses are being used by CBL-Mariner's packages and where the package may be derived from. The license files include the following files:
+* LICENSE-MAP files are up-to-date. These files indicate which licenses are being used by Azure Linux's packages and where the package may be derived from. The license files include the following files:
   * ./SPECS/LICENSES-AND-NOTICES/data/licenses.json
   * ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md
 
@@ -206,4 +206,4 @@ When creating your PR, please ensure the following:
 
 ## Bugs
 
-If the bug is security related, please use the [security guidelines](#security-vulnerabilities) above. Otherwise, please use the [issues page](https://github.com/microsoft/CBL-Mariner/issues) on CBL-Mariner to file bugs.
+If the bug is security related, please use the [security guidelines](#security-vulnerabilities) above. Otherwise, please use the [issues page](https://github.com/microsoft/azurelinux/issues) on Azure Linux to file bugs.

README.md

@@ -1,25 +1,25 @@
-# CBL-Mariner
+# Azure Linux
 
-CBL-Mariner is an internal Linux distribution for Microsoft’s cloud infrastructure and edge products and services. CBL-Mariner is designed to provide a consistent platform for these devices and services and will enhance Microsoft’s ability to stay current on Linux updates. This initiative is part of Microsoft’s increasing investment in a wide range of Linux technologies, such as [SONiC](https://azure.microsoft.com/en-us/blog/sonic-the-networking-switch-software-that-powers-the-microsoft-global-cloud/) and [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/about). CBL-Mariner is being shared publicly as part of Microsoft’s commitment to Open Source and to contribute back to the Linux community. CBL-Mariner does not change our approach or commitment to any existing third-party Linux distribution offerings.
+Azure Linux is an internal Linux distribution for Microsoft’s cloud infrastructure and edge products and services. Azure Linux is designed to provide a consistent platform for these devices and services and will enhance Microsoft’s ability to stay current on Linux updates. This initiative is part of Microsoft’s increasing investment in a wide range of Linux technologies, such as [SONiC](https://azure.microsoft.com/en-us/blog/sonic-the-networking-switch-software-that-powers-the-microsoft-global-cloud/) and [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/about). Azure Linux is being shared publicly as part of Microsoft’s commitment to Open Source and to contribute back to the Linux community. Azure Linux does not change our approach or commitment to any existing third-party Linux distribution offerings.
 
-CBL-Mariner has been engineered with the notion that a small common core set of packages can address the universal needs of first party cloud and edge services while allowing individual teams to layer additional packages on top of the common core to produce images for their workloads. This is made possible by a simple build system that enables:
+Azure Linux has been engineered with the notion that a small common core set of packages can address the universal needs of first party cloud and edge services while allowing individual teams to layer additional packages on top of the common core to produce images for their workloads. This is made possible by a simple build system that enables:
 
 - **Package Generation:** This produces the desired set of RPM packages from SPEC files and source files.
 - **Image Generation:** This produces the desired image artifacts like ISOs or VHDs from a given set of packages.
 
-Whether deployed as a container or a container host, CBL-Mariner consumes limited disk and memory resources. The lightweight characteristics of CBL-Mariner also provides faster boot times and a minimal attack surface. By focusing the features in the core image to just what is needed for our internal cloud customers there are fewer services to load, and fewer attack vectors.
+Whether deployed as a container or a container host, Azure Linux consumes limited disk and memory resources. The lightweight characteristics of Azure Linux also provides faster boot times and a minimal attack surface. By focusing the features in the core image to just what is needed for our internal cloud customers there are fewer services to load, and fewer attack vectors.
 
-When security vulnerabilities arise, CBL-Mariner supports both a package-based update model and an image based update model.  Leveraging the common [RPM Package Manager](https://rpm.org/) system, CBL-Mariner makes the latest security patches and fixes available for download with the goal of fast turn-around times.
+When security vulnerabilities arise, Azure Linux supports both a package-based update model and an image based update model.  Leveraging the common [RPM Package Manager](https://rpm.org/) system, Azure Linux makes the latest security patches and fixes available for download with the goal of fast turn-around times.
 
-## Getting Started with CBL-Mariner
+## Getting Started with Azure Linux
 
 ### Build
 
-Instructions for building CBL-Mariner may be found here: [Toolkit Documentation](./toolkit/README.md).
+Instructions for building Azure Linux may be found here: [Toolkit Documentation](./toolkit/README.md).
 
 ### ISO
 
-You can try CBL-Mariner with the following ISO images:
+You can try Azure Linux with the following ISO images:
 
 - [Mariner 2.0 x86_64 ISO](https://aka.ms/mariner-2.0-x86_64-iso).
 - [Mariner 1.0 x86_64 ISO](https://aka.ms/mariner-1.0-x86_64-iso).
@@ -28,7 +28,7 @@ Before using a downloaded ISO, [verify the checksum and signature of the image](
 
 After downloading the ISO, use [the quickstart instructions](toolkit/docs/quick_start/quickstart.md) to install and use the image in a Hyper-V VM.
 
-Note: Support for the ISO is community based. Before filing a new bug or feature request, please search the list of Github Issues. If you are unable to find a matching issue, please report new bugs by clicking [here](https://github.com/microsoft/CBL-Mariner/issues) or create a new feature request by clicking [here](https://github.com/microsoft/CBL-Mariner/issues/new). For additional information refer to the [support.md](https://github.com/microsoft/CBL-Mariner/blob/2.0/SUPPORT.md) file.
+Note: Support for the ISO is community based. Before filing a new bug or feature request, please search the list of Github Issues. If you are unable to find a matching issue, please report new bugs by clicking [here](https://github.com/microsoft/azurelinux/issues) or create a new feature request by clicking [here](https://github.com/microsoft/azurelinux/issues/new). For additional information refer to the [support.md](https://github.com/microsoft/azurelinux/blob/3.0/SUPPORT.md) file.
 
 
 ## Getting Help
@@ -46,7 +46,7 @@ This project may contain trademarks or logos for projects, products, or services
 
 ## Acknowledgments
 
-Any Linux distribution, including CBL-Mariner, benefits from contributions by the open software community. We gratefully acknowledge all contributions made from the broader open source community, in particular:
+Any Linux distribution, including Azure Linux, benefits from contributions by the open software community. We gratefully acknowledge all contributions made from the broader open source community, in particular:
 
 1) The [Photon OS Project](https://vmware.github.io/photon/) for SPEC files originating from the Photon distribution.
 

SPECS/LICENSES-AND-NOTICES/data/licenses.json

@@ -1,5 +1,5 @@
 {
-    "header": "The CBL-Mariner SPEC files originated from a variety of sources with varying licenses.  The changelog for each SPEC file declares provenance for CBL-Mariner.  Some of the SPEC files that originated from other distributions might already have been derived from alternate sources. Their licenses can be found in LICENSE-EXCEPTION.xxx files in this folder.",
+    "header": "The Azure Linux SPEC files originated from a variety of sources with varying licenses.  The changelog for each SPEC file declares provenance for Azure Linux.  Some of the SPEC files that originated from other distributions might already have been derived from alternate sources. Their licenses can be found in LICENSE-EXCEPTION.xxx files in this folder.",
     "table_headers": [
         "Origin",
         "License",

SPECS/tboot/README.md

@@ -1,9 +1,9 @@
-# CBL-Mariner TBOOT
+# Azure Linux TBOOT
 
 Platform Prerequisites: Real hardware platform that supports Intel TXT (Trusted Execution Technology) and TPM 2.0
 --------------------------
 
-Enabling TBOOT in CBL-Mariner:
+Enabling TBOOT in Azure Linux:
 1. Install the tboot rpm package
 
 2. Check the cpu info of the platform and download the corresponding SINIT ACM module from: https://www.intel.com/content/www/us/en/developer/articles/tool/intel-trusted-execution-technology.html to /boot

SUPPORT.md

@@ -4,14 +4,14 @@
 
 This project uses [GitHub issues][gh-issue] to [track bugs][gh-bug] and [feature requests][gh-feature]. Please search the existing issues before filing new issues to avoid duplicates. For new topics, file your bug or feature request as a new issue.
 
-For questions about using this project, please look at the [Tutorials repo for CBL-Mariner][tutorial] and our [Contributor's Guide][contributor] if you want to work on CBL-Mariner.
+For questions about using this project, please look at the [Tutorials repo for Azure Linux][tutorial] and our [Contributor's Guide][contributor] if you want to work on Azure Linux.
 
 ## Microsoft Support Policy
 
-Support for CBL-Mariner is limited to the resources listed above.
+Support for Azure Linux is limited to the resources listed above.
 
-[gh-issue]: https://github.com/microsoft/CBL-Mariner/issues/new/choose
-[gh-bug]: https://github.com/microsoft/CBL-Mariner/issues/new?labels=bug
-[gh-feature]: https://github.com/microsoft/CBL-Mariner/issues/new?labels=enhancement
-[tutorial]: https://github.com/Microsoft/CBL-MarinerTutorials
-[contributor]: https://github.com/microsoft/CBL-Mariner/blob/main/CONTRIBUTING.md
+[gh-issue]: https://github.com/microsoft/azurelinux/issues/new/choose
+[gh-bug]: https://github.com/microsoft/azurelinux/issues/new?labels=bug
+[gh-feature]: https://github.com/microsoft/azurelinux/issues/new?labels=enhancement
+[tutorial]: https://github.com/microsoft/azurelinux-Tutorials
+[contributor]: https://github.com/microsoft/azurelinux/blob/main/CONTRIBUTING.md