As a long-time user, I second Alan's concerns. Reproducibility of cloud images doesn't seem to be a priority for the major distros, and at best, the marketplace throws up a roadblock requiring acceptance through the AWS dashboard when setting up a new account.<br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 10, 2016 at 10:53 AM Alan Ivey <<a href="mailto:alanivey@gmail.com">alanivey@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="font-size:12.8px">Hi everyone,</span><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">I'd like to revisit the thread about how the CentOS 7 AMIs are created (</span><a href="https://lists.centos.org/pipermail/centos-devel/2015-July/013652.html" style="font-size:12.8px" target="_blank">https://lists.centos.org/pipermail/centos-devel/2015-July/013652.html</a><span style="font-size:12.8px">) and see if the process can be published in the </span><a href="https://github.com/CentOS/sig-cloud-instance-build" style="font-size:12.8px" target="_blank">https://github.com/CentOS/sig-cloud-instance-build</a><span style="font-size:12.8px"> repository or another relevant location.</span><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">With CentOS 7 AMIs only being available in the Marketplace, all resulting EC2 instances have the Marketplace codes attached to the EBS volumes. A significant restriction of this is that a resulting image cannot be the non-primary volume of an instance unless it is powered down. This presents itself to be a problem in at least the following scenarios:</div><div style="font-size:12.8px"><ul><li style="margin-left:15px">Unable to attach a CentOS 7 boot volume to another instance for repair without either creating a temporary instance or shutting down an existing one. For example, if you messed up the /etc/sudoers file and logged out, and wanted to repair, you would not be able to repair by mounting to another instance and editing the file without incurring additional (albeit small) cost, or having an existing instance be temporarily unavailable. </li><li style="margin-left:15px">The "amazon-chroot" Packer Builder (<a href="https://www.packer.io/docs/builders/amazon-chroot.html" target="_blank">https://www.packer.io/docs/builders/amazon-chroot.html</a>) does not work because it starts by mounting a copy of the snapshot tied to the AMI as part of a scripted operation and therefore cannot power off to do so</li></ul><div><span style="font-size:12.8px">Custom AMIs, snapshots, copied EBS volumes, etc, all have the marketplace codes copied to them and inherit the restrictions. If an org was to use these features for automating environments and was disconnected from the original Marketplace agreement, they may be unaware of this limitation.</span><br></div><div><br></div><div>I would also appreciate being able to have the additional transparency of seeing how an AWS AMI is created as the docker/openstack/etc images from the repository referenced above. This would be useful in environments with regulatory compliance concerns, such as AWS GovCloud, HIPAA, FedRAMP, etc. <br></div><div><br></div><div>I understand the benefit that Marketplace registrations allow for the ability to notify users of any changes, and I am not necessarily advocating for switching away from the Marketplace as the primary AMI location. I would like to be provided the opportunity to build a private AMI in the exact same procedure as the official image so as to avert the restrictions provided by the Marketplace.</div></div><div style="font-size:12.8px"><br></div><div><i style="font-size:12.8px">[Note: I previously posted this question to <a href="https://lists.centos.org/pipermail/centos-virt/2016-February/004907.html" target="_blank">centos-virt</a>, but I did not receive any feedback and I have since noticed that </i><span style="font-size:12.8px"><i><a href="https://wiki.centos.org/SpecialInterestGroup/Cloud" target="_blank">https://wiki.centos.org/SpecialInterestGroup/Cloud</a> refers to the CentOS-Devel list for discussion. My apologies to subscribers of both lists.</i></span><i style="font-size:12.8px">]</i></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Thank you,</div><div style="font-size:12.8px">Alan</div></div></div>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</blockquote></div>