dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
The images currently pull from the compose repo:
```
url=https://kojipkgs.fedoraproject.org/compose/ostree/27/
```
This is where they are built from. We need to figure out what location we want to promote content to and have that be our 'prod' location in our images. Ideally would be nice to make this change before we ship f27 so that we don't have to tell our users to update the url.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/373
davdunc added a new comment to an issue you are following:
``
Let's take into account several NVMe related requirements as well.
It is recommended that the nvme.io.timeout value be set to a high number. This requires the following patch, accepted in 4.14: http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.htmlhttp://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html shows setting a high timeout for the nvme devices as well. This is set to the uint_max in Amazon Linux because it is expected that when the instance becomes available, the volume will be available as well.
With Amazon Linux AMI 2017.09.01 or later, you can run the __ebsnvme-id__ command to map the NVMe device name to a volume ID and device name. This is a part of the __ec2-utils__ applications included in the Amazon Linux source and will be a helpful thing to incorporate for support of the C5 and future instance types.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/271