Skip to content

Conversation

@AleksaSvitlica
Copy link
Contributor

I tested and confirmed the instructions work for Pro FIPS 22.04 and Pro FIPS 20.04.

Update to use Sphinx's code-block directive to get better syntax
highlighting.
Updates the guide for creating golden images to work for Ubuntu 22.04
and newer. There are differences in the underlying offers using from
22.04 onward which require some changes to the instructions. These
differences mean the image publisher/offer/sku is not included in the
attested metadata and therefore attaching to Pro requires some
additional steps.
subscriptionID=$(az account show --query id --output tsv)
Create a variable for your subscription ID:
Create variables for gallery name, image definition name and Ubuntu Pro plan to be used. If you have an Ubuntu Pro private offer with Canonical that includes 24x7 technical support with SLAs, you'll have a custom offer and SKU, which can be used here. If not, as seen in the example below, you can use any Pro image that is publicly available at the Azure Marketplace. The image will be displayed in the Azure Portal as ``sigName/imageDefName``.
Copy link
Contributor

Choose a reason for hiding this comment

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

A link to the find-Ubuntu-images-on-Azure how-to would be helpful here.

Comment on lines +186 to +192
--publisher $ProPlanPublisher \
--offer $ProPlanOffer \
--sku $ProPlanSku \
--os-type Linux \
--plan-name $ProPlanSku \
--plan-product $ProPlanOffer \
--plan-publisher $ProPlanPublisher \
Copy link
Contributor

Choose a reason for hiding this comment

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

How do publisher, offer, and sku differ from plan-publisher, plan-product, and plan-name?

jq 'del(.properties.source.planInfo)' $imageTemplateFile > temp.json && mv temp.json $imageTemplateFile
Copy link
Contributor

Choose a reason for hiding this comment

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

Superfluous empty line

--ssh-key-values $SSHPublicKeyPath \
--public-ip-sku Standard
Copy link
Contributor

Choose a reason for hiding this comment

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

Superfluous empty line

--generate-ssh-keys \
--public-ip-sku Standard
Copy link
Contributor

Choose a reason for hiding this comment

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

Superfluous empty line

}
You can use the ``publicIpAddress`` (``51.143.126.x`` in this case) to ssh into the machine. To check that the VM is attached to an Ubuntu Pro subscription and is running a FIPS kernel, run:
You can use the ``publicIpAddress`` (``51.143.126.x`` in this case) to ssh into the machine. Using the following instructions to attach the VM to an Ubuntu Pro subscription:
Copy link
Contributor

Choose a reason for hiding this comment

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

At this point, I think we should explicitly differentiate between < 22.04 and >= 22.04. The end user should understand what to expect regardless of whether they are using an image from one of the example lines in this document.

sudo pro status --wait
.. code-block:: sh
az vm update \
Copy link
Contributor

Choose a reason for hiding this comment

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

This manual post-launch intervention would be less than ideal in an auto-scaling setting. As discussed over Mattermost, we may want to instead removing the instruction to detach. Let's discuss offline tomorrow.

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.

2 participants