Hi,
I am a user of CentOS 8. When can we expect an image on AWS? I am just learning AWS and would like to use CentOS 8 for that.
https://wiki.centos.org/SpecialInterestGroup/CloudInstance
says that this is the list to ask.
thanks
--- Lee
On 16/05/2020 16:20, Thomas Stephen Lee wrote:
Hi,
I am a user of CentOS 8. When can we expect an image on AWS? I am just learning AWS and would like to use CentOS 8 for that.
https://wiki.centos.org/SpecialInterestGroup/CloudInstance
says that this is the list to ask.
thanks
Lee
we built CentOS 8 AMI for both x86_64 and aarch64 and I was able to import these images in our own account, and could boot these images fine. We tried to reach out to AWS multiple times but no answer so actually I'd be tempted to just share for 8.2.2004 release the AMIs and announce that nobody can use marketplace but can directly launched shared AMIs when the have the reference , so like what Fedora is doing (we never were able to get the 8.0.1905 nor 8.1911 images published on marketplace) :-(
On Sat, May 16, 2020 at 5:07 PM Fabian Arrotin arrfab@centos.org wrote:
On 16/05/2020 16:20, Thomas Stephen Lee wrote:
Hi,
I am a user of CentOS 8. When can we expect an image on AWS? I am just learning AWS and would like to use CentOS 8 for that.
https://wiki.centos.org/SpecialInterestGroup/CloudInstance
says that this is the list to ask.
thanks
Lee
we built CentOS 8 AMI for both x86_64 and aarch64 and I was able to import these images in our own account, and could boot these images fine. We tried to reach out to AWS multiple times but no answer so actually I'd be tempted to just share for 8.2.2004 release the AMIs and announce that nobody can use marketplace but can directly launched shared AMIs when the have the reference , so like what Fedora is doing (we never were able to get the 8.0.1905 nor 8.1911 images published on marketplace) :-(
Can you outline the problems that prevent including Centos8 AMI under https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde-8f34... ? Who publishes the image updates there? When the final decision is made it would be good to update https://bugs.centos.org/view.php?id=16614
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Sat, May 16, 2020 at 11:07 AM Fabian Arrotin arrfab@centos.org wrote:
On 16/05/2020 16:20, Thomas Stephen Lee wrote:
Hi,
I am a user of CentOS 8. When can we expect an image on AWS? I am just learning AWS and would like to use CentOS 8 for that.
https://wiki.centos.org/SpecialInterestGroup/CloudInstance
says that this is the list to ask.
thanks
Lee
we built CentOS 8 AMI for both x86_64 and aarch64 and I was able to import these images in our own account, and could boot these images fine. We tried to reach out to AWS multiple times but no answer so actually I'd be tempted to just share for 8.2.2004 release the AMIs and announce that nobody can use marketplace but can directly launched shared AMIs when the have the reference , so like what Fedora is doing (we never were able to get the 8.0.1905 nor 8.1911 images published on marketplace) :-(
I've done it by hand now, for CentOS 8 and RHEL 8, by building locally on VirtualBox or VMware Player from installation media and exporting a VM image to import on for an AWSM AMI. It does require some caution: encrypting your root disk images, for example, is considered a good security step. But XFS on CentOS 7 used to present some difficulties, and I wound engaging in some serious "use my own tools to transfer the running OS to a pristine new disk image partitioned the way my client demanded to follow their security standards. I've been pulling that stunt since roughly 1998 when updating and repartitioning operating systeems for a Very Large CDN, the experience is helpful for dealing with mock and chroot dcages.
On Sun, May 17, 2020 at 4:35 AM Nico Kadel-Garcia nkadel@gmail.com wrote:
On Sat, May 16, 2020 at 11:07 AM Fabian Arrotin arrfab@centos.org wrote:
On 16/05/2020 16:20, Thomas Stephen Lee wrote:
Hi,
I am a user of CentOS 8. When can we expect an image on AWS? I am just learning AWS and would like to use CentOS 8 for that.
https://wiki.centos.org/SpecialInterestGroup/CloudInstance
says that this is the list to ask.
thanks
Lee
we built CentOS 8 AMI for both x86_64 and aarch64 and I was able to import these images in our own account, and could boot these images fine. We tried to reach out to AWS multiple times but no answer so actually I'd be tempted to just share for 8.2.2004 release the AMIs and announce that nobody can use marketplace but can directly launched shared AMIs when the have the reference , so like what Fedora is doing (we never were able to get the 8.0.1905 nor 8.1911 images published on marketplace) :-(
I've done it by hand now, for CentOS 8 and RHEL 8, by building locally on VirtualBox or VMware Player from installation media and exporting a VM image to import on for an AWSM AMI. It does require some caution: encrypting your root disk images, for example, is considered a good security step. But XFS on CentOS 7 used to present some difficulties, and I wound engaging in some serious "use my own tools to transfer the running OS to a pristine new disk image partitioned the way my client demanded to follow their security standards. I've been pulling that stunt since roughly 1998 when updating and repartitioning operating systeems for a Very Large CDN, the experience is helpful for dealing with mock and chroot dcages. _______________________________________________
Hi,
Can Red Hat/IBM/Community do something to help?
thanks
--- Lee
On Sat, May 16, 2020 at 11:58 PM Thomas Stephen Lee lee.iitb@gmail.com wrote:
On Sun, May 17, 2020 at 4:35 AM Nico Kadel-Garcia nkadel@gmail.com wrote:
On Sat, May 16, 2020 at 11:07 AM Fabian Arrotin arrfab@centos.org wrote:
On 16/05/2020 16:20, Thomas Stephen Lee wrote:
Hi,
I am a user of CentOS 8. When can we expect an image on AWS? I am just learning AWS and would like to use CentOS 8 for that.
https://wiki.centos.org/SpecialInterestGroup/CloudInstance
says that this is the list to ask.
thanks
Lee
we built CentOS 8 AMI for both x86_64 and aarch64 and I was able to import these images in our own account, and could boot these images fine. We tried to reach out to AWS multiple times but no answer so actually I'd be tempted to just share for 8.2.2004 release the AMIs and announce that nobody can use marketplace but can directly launched shared AMIs when the have the reference , so like what Fedora is doing (we never were able to get the 8.0.1905 nor 8.1911 images published on marketplace) :-(
I've done it by hand now, for CentOS 8 and RHEL 8, by building locally on VirtualBox or VMware Player from installation media and exporting a VM image to import on for an AWSM AMI. It does require some caution: encrypting your root disk images, for example, is considered a good security step. But XFS on CentOS 7 used to present some difficulties, and I wound engaging in some serious "use my own tools to transfer the running OS to a pristine new disk image partitioned the way my client demanded to follow their security standards. I've been pulling that stunt since roughly 1998 when updating and repartitioning operating systeems for a Very Large CDN, the experience is helpful for dealing with mock and chroot dcages. _______________________________________________
Hi,
Can Red Hat/IBM/Community do something to help?
thanks
Sharing a popular AMI out of your own personal account can become.... expensive, for an individual, especially if it's a bit on the buiky side with graphical applications or development tools. There also may be bureaucratic or business goal reasons for AWS to delay CentOs 8: I hope there is no subtle interference going on behind closed doors.
I have Packer and shell scripts for using the official RHEL8 AMIs for x86_64 and aarch64 to create minimal (with a couple of AWS-specific tools; search "optional" in the shell script) CentOS 8 AMIs. Hopefully this is helpful to others: https://gist.github.com/alanivey/68712e6172b793037fbd77ebb3112c3f
On Sun, May 17, 2020 at 4:41 AM Nico Kadel-Garcia nkadel@gmail.com wrote:
On Sat, May 16, 2020 at 11:58 PM Thomas Stephen Lee lee.iitb@gmail.com wrote:
On Sun, May 17, 2020 at 4:35 AM Nico Kadel-Garcia nkadel@gmail.com
wrote:
On Sat, May 16, 2020 at 11:07 AM Fabian Arrotin arrfab@centos.org
wrote:
On 16/05/2020 16:20, Thomas Stephen Lee wrote:
Hi,
I am a user of CentOS 8. When can we expect an image on AWS? I am just learning AWS and would like to use CentOS 8 for that.
https://wiki.centos.org/SpecialInterestGroup/CloudInstance
says that this is the list to ask.
thanks
Lee
we built CentOS 8 AMI for both x86_64 and aarch64 and I was able to import these images in our own account, and could boot these images
fine.
We tried to reach out to AWS multiple times but no answer so actually I'd be tempted to just share for 8.2.2004 release the AMIs and
announce
that nobody can use marketplace but can directly launched shared AMIs when the have the reference , so like what Fedora is doing (we never were able to get the 8.0.1905 nor 8.1911 images published on marketplace) :-(
I've done it by hand now, for CentOS 8 and RHEL 8, by building locally on VirtualBox or VMware Player from installation media and exporting a VM image to import on for an AWSM AMI. It does require some caution: encrypting your root disk images, for example, is considered a good security step. But XFS on CentOS 7 used to present some difficulties, and I wound engaging in some serious "use my own tools to transfer the running OS to a pristine new disk image partitioned the way my client demanded to follow their security standards. I've been pulling that stunt since roughly 1998 when updating and repartitioning operating systeems for a Very Large CDN, the experience is helpful for dealing with mock and chroot dcages. _______________________________________________
Hi,
Can Red Hat/IBM/Community do something to help?
thanks
Sharing a popular AMI out of your own personal account can become.... expensive, for an individual, especially if it's a bit on the buiky side with graphical applications or development tools. There also may be bureaucratic or business goal reasons for AWS to delay CentOs 8: I hope there is no subtle interference going on behind closed doors. _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Why bother with any of this. You should build your own images and this is exactly what Image Builder does using lorax/andconda. You can use the same templates to create consistent images across AWS, GCP, Azure and more.
For AWS you might need a couple of RPMs - ec2-utils and ec2-net-utils and maybe another if you want to use instance connect. Just get the src RPMs from an Amazon Linux 2 image, rebuild the RPMS for CentOS8. You don't even need to do any blueprint configs just modify the kickstart templates and you are good to go.
Here's one I put together for a base AMI. Idiomatic and much cleaner that packer. You can build both arm64 and x86_64.
https://gist.github.com/ak2196/53ee89c039f41b3701ba04e89aa72068
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/htm...
On Sun, May 24, 2020 at 9:50 AM Alan Ivey alanivey@gmail.com wrote:
I have Packer and shell scripts for using the official RHEL8 AMIs for x86_64 and aarch64 to create minimal (with a couple of AWS-specific tools; search "optional" in the shell script) CentOS 8 AMIs. Hopefully this is helpful to others: https://gist.github.com/alanivey/68712e6172b793037fbd77ebb3112c3f
On Sun, May 17, 2020 at 4:41 AM Nico Kadel-Garcia nkadel@gmail.com wrote:
On Sat, May 16, 2020 at 11:58 PM Thomas Stephen Lee lee.iitb@gmail.com wrote:
On Sun, May 17, 2020 at 4:35 AM Nico Kadel-Garcia nkadel@gmail.com
wrote:
On Sat, May 16, 2020 at 11:07 AM Fabian Arrotin arrfab@centos.org
wrote:
On 16/05/2020 16:20, Thomas Stephen Lee wrote:
Hi,
I am a user of CentOS 8. When can we expect an image on AWS? I am just learning AWS and would like to use CentOS 8 for that.
https://wiki.centos.org/SpecialInterestGroup/CloudInstance
says that this is the list to ask.
thanks
Lee
we built CentOS 8 AMI for both x86_64 and aarch64 and I was able to import these images in our own account, and could boot these images
fine.
We tried to reach out to AWS multiple times but no answer so actually I'd be tempted to just share for 8.2.2004 release the AMIs and
announce
that nobody can use marketplace but can directly launched shared AMIs when the have the reference , so like what Fedora is doing (we never were able to get the 8.0.1905 nor 8.1911 images published on marketplace) :-(
I've done it by hand now, for CentOS 8 and RHEL 8, by building locally on VirtualBox or VMware Player from installation media and exporting a VM image to import on for an AWSM AMI. It does require some caution: encrypting your root disk images, for example, is considered a good security step. But XFS on CentOS 7 used to present some difficulties, and I wound engaging in some serious "use my own tools to transfer the running OS to a pristine new disk image partitioned the way my client demanded to follow their security standards. I've been pulling that stunt since roughly 1998 when updating and repartitioning operating systeems for a Very Large CDN, the experience is helpful for dealing with mock and chroot dcages. _______________________________________________
Hi,
Can Red Hat/IBM/Community do something to help?
thanks
Sharing a popular AMI out of your own personal account can become.... expensive, for an individual, especially if it's a bit on the buiky side with graphical applications or development tools. There also may be bureaucratic or business goal reasons for AWS to delay CentOs 8: I hope there is no subtle interference going on behind closed doors. _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 24/05/2020 15:49, Alan Ivey wrote:
I have Packer and shell scripts for using the official RHEL8 AMIs for x86_64 and aarch64 to create minimal (with a couple of AWS-specific tools; search "optional" in the shell script) CentOS 8 AMIs. Hopefully this is helpful to others: https://gist.github.com/alanivey/68712e6172b793037fbd77ebb3112c3f
<snip>
As said in this thread, the problem isn't to build AMI (as we have done that and the kickstart files are even publicly available at https://git.centos.org/centos/kickstarts/tree/master, and we tested for both x86_64 and aarch64 architectures) but the problem is having those imported into Marketplace .....
Fabian,
If you could share some details I'd be happy to take a crack at getting someone at AWS Marketplace to take a look.
On Mon, May 25, 2020 at 2:13 AM Fabian Arrotin arrfab@centos.org wrote:
On 24/05/2020 15:49, Alan Ivey wrote:
I have Packer and shell scripts for using the official RHEL8 AMIs for x86_64 and aarch64 to create minimal (with a couple of AWS-specific tools; search "optional" in the shell script) CentOS 8 AMIs. Hopefully this is helpful to others: https://gist.github.com/alanivey/68712e6172b793037fbd77ebb3112c3f
<snip>
As said in this thread, the problem isn't to build AMI (as we have done that and the kickstart files are even publicly available at https://git.centos.org/centos/kickstarts/tree/master, and we tested for both x86_64 and aarch64 architectures) but the problem is having those imported into Marketplace .....
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 25/05/2020 11:14, Akshay Kumar wrote:
Fabian,
If you could share some details I'd be happy to take a crack at getting someone at AWS Marketplace to take a look.
If you have an AMI there and can import + run, what is the major hurdle to using them ?
ie, why do you need the image in the marketplace from a user standpoint ?
Regards
I moved to image builder a while go to get out of the image publishing delays so this doesn't affect me at all. Fabian mentioned not being able to get a hold of anyone in marketplace. I can help with that so if that's a sticking point why not let someone else take a crack at it.
On Mon, May 25, 2020 at 7:32 AM Karanbir Singh kbsingh@centos.org wrote:
On 25/05/2020 11:14, Akshay Kumar wrote:
Fabian,
If you could share some details I'd be happy to take a crack at getting someone at AWS Marketplace to take a look.
If you have an AMI there and can import + run, what is the major hurdle to using them ?
ie, why do you need the image in the marketplace from a user standpoint ?
Regards
On 25/05/2020 12:36, Akshay Kumar wrote:
I moved to image builder a while go to get out of the image publishing delays so this doesn't affect me at all. Fabian mentioned not being able to get a hold of anyone in marketplace. I can help with that so if that's a sticking point why not let someone else take a crack at it.
Fair.
the main goal from an infra standpoint for anyone should really be to unify their stack, in AWS or GCP or AZure or on-prem openstack / self managed etc and we've largley optimised for that. the Monthly cloud images should be the unified piece here, for folks not wanting to build themselves.
the market place piece is a longer conversation, were talking to aws later this week about that. lets see what progress we can make there.
regards,
On 5/25/20 5:02 AM, Karanbir Singh wrote:
the main goal from an infra standpoint for anyone should really be to unify their stack, in AWS or GCP or AZure or on-prem openstack / self managed etc and we've largley optimised for that. the Monthly cloud images should be the unified piece here, for folks not wanting to build themselves.
the market place piece is a longer conversation, were talking to aws later this week about that. lets see what progress we can make there.
Is there any possibility of having AWS images published both as AMIs *and* in the AWS Marketplace? Similar to what was done for CentOS 7 [1], and what's being done for Fedora [2] ?
I can see where Marketplace might be attractive for some, but it carries a bit of baggage with it due to the subscription model that it imposes -- even if the subscription charge is $0 as would presumably be the case for CentOS. Perhaps Marketplace has become easier to work with in recent years, but I know I've run into issues due to how Marketplaces uses product codes and implements restrictions as to what can be done with volumes and snapshots (for those who might want to modify the issue and create modified AMIs). [3]
[1] https://wiki.centos.org/Cloud/AWS [2] https://alt.fedoraproject.org/cloud/ [3] https://www.caseylabs.com/remove-the-aws-marketplace-code-from-a-centos-ami/
-Greg
On 25/05/2020 14:48, Greg Bailey wrote:
Is there any possibility of having AWS images published both as AMIs *and* in the AWS Marketplace? Similar to what was done for CentOS 7 [1], and what's being done for Fedora [2] ?
the generic cloud image in CentOS Linux 6 and 7 was always compatible with the AMI ( it is essentially the same image, just imported and registered )
thats the goal I want to get to in CentOS Linux 8 as well, we've just had lots of teething issues getting there.
regards,
Am 26.05.20 um 13:01 schrieb Karanbir Singh:
On 25/05/2020 14:48, Greg Bailey wrote:
Is there any possibility of having AWS images published both as AMIs *and* in the AWS Marketplace? Similar to what was done for CentOS 7 [1], and what's being done for Fedora [2] ?
the generic cloud image in CentOS Linux 6 and 7 was always compatible with the AMI ( it is essentially the same image, just imported and registered )
thats the goal I want to get to in CentOS Linux 8 as well, we've just had lots of teething issues getting there.
I read through this mail thread and because I am not familiar with AWS I have still some questions:
Is it possible to use (upload) this images to create instances in AWS?
https://cloud.centos.org/centos/8/x86_64/images/
I known that the CentOS team is hard working on 8.2.2004 but any progress in getting C8 to AWS Market Place? Are the plans to having the Official Public Images published with the release of 8.2.2004?
Thanks, Leon
On 10/06/2020 17:08, Leon Fauster via CentOS-devel wrote:
Am 26.05.20 um 13:01 schrieb Karanbir Singh:
On 25/05/2020 14:48, Greg Bailey wrote:
<snip>
Is it possible to use (upload) this images to create instances in AWS?
https://cloud.centos.org/centos/8/x86_64/images/
I known that the CentOS team is hard working on 8.2.2004 but any progress in getting C8 to AWS Market Place? Are the plans to having the Official Public Images published with the release of 8.2.2004?
Not with the currently pushed ones, but we fixed the kickstart files used to generate the EC2 cloud images so the ones that will be generated for 8.2.2004 so the new ones should work for this.
While we still don't have clear path/access to publish to AWS Market Place, we can try to have shared AMIs (public) and public ID per region ... that should at least help help deploying from our centos official images, instead of random images that pretend to be centos on marketplace
Hopefully we'll be able to announce that as soon as we'll have all that built and tested (and should be really soon now)
On 6/10/20 1:49 PM, Fabian Arrotin wrote:
On 10/06/2020 17:08, Leon Fauster via CentOS-devel wrote:
Am 26.05.20 um 13:01 schrieb Karanbir Singh:
On 25/05/2020 14:48, Greg Bailey wrote:
<snip> > Is it possible to use (upload) this images to create instances in AWS? > > https://cloud.centos.org/centos/8/x86_64/images/ > > I known that the CentOS team is hard working on 8.2.2004 but any > progress in getting C8 to AWS Market Place? Are the plans to having > the Official Public Images published with the release of 8.2.2004? > Not with the currently pushed ones, but we fixed the kickstart files used to generate the EC2 cloud images so the ones that will be generated for 8.2.2004 so the new ones should work for this.
Where's the fix captured? I checked https://github.com/CentOS/sig-cloud-instance-build but I don't see any commits since December. Maybe I'm looking in the wrong repo?
While we still don't have clear path/access to publish to AWS Market Place, we can try to have shared AMIs (public) and public ID per region
This would be great; consuming known public AMIs is easier than having to subscribe every account to the marketplace. IMHO the marketplace feels like it's really better suited for proprietary software--I don't like the idea of having to "register" every account that I might want to run CentOS VMs on.
... that should at least help help deploying from our centos official images, instead of random images that pretend to be centos on marketplace
Hopefully we'll be able to announce that as soon as we'll have all that built and tested (and should be really soon now)
Awesome; thanks!
-Greg
On 10/06/2020 17:08, Leon Fauster via CentOS-devel wrote:
Am 26.05.20 um 13:01 schrieb Karanbir Singh:
On 25/05/2020 14:48, Greg Bailey wrote:
<snip>
Is it possible to use (upload) this images to create instances in AWS?
https://cloud.centos.org/centos/8/x86_64/images/
I known that the CentOS team is hard working on 8.2.2004 but any progress in getting C8 to AWS Market Place? Are the plans to having the Official Public Images published with the release of 8.2.2004?
Not with the currently pushed ones, but we fixed the kickstart files used to generate the EC2 cloud images so the ones that will be generated for 8.2.2004 so the new ones should work for this.
While we still don't have clear path/access to publish to AWS Market Place, we can try to have shared AMIs (public) and public ID per region ... that should at least help help deploying from our centos official images, instead of random images that pretend to be centos on marketplace
Hopefully we'll be able to announce that as soon as we'll have all that built and tested (and should be really soon now)
Am 10.06.20 um 22:49 schrieb Fabian Arrotin:
On 10/06/2020 17:08, Leon Fauster via CentOS-devel wrote:
Am 26.05.20 um 13:01 schrieb Karanbir Singh:
On 25/05/2020 14:48, Greg Bailey wrote:
<snip> > > Is it possible to use (upload) this images to create instances in AWS? > > https://cloud.centos.org/centos/8/x86_64/images/ > > I known that the CentOS team is hard working on 8.2.2004 but any > progress in getting C8 to AWS Market Place? Are the plans to having > the Official Public Images published with the release of 8.2.2004? >
Not with the currently pushed ones, but we fixed the kickstart files used to generate the EC2 cloud images so the ones that will be generated for 8.2.2004 so the new ones should work for this.
Ah okay, thanks. I assume that you mean this one (CentOS-8-EC2.ks):
https://git.centos.org/centos/kickstarts/tree/master
Can I use this ks file to compose an new image with lorax? Or are some other tools missing / unseen by me to build a working image?
I would like to start right away booting some instances for testing proposes.
BTW, in the meanwhile I was already elaborating the workflow of importing images into my aws account. thereby i noticed that ec2 import-snapshot does not support the qcow2 disk format. The next supported format would be "raw" ... still elaborating the workflow ...
While we still don't have clear path/access to publish to AWS Market Place, we can try to have shared AMIs (public) and public ID per region ... that should at least help help deploying from our centos official images, instead of random images that pretend to be centos on marketplace
This sounds reasonable.
Hopefully we'll be able to announce that as soon as we'll have all that built and tested (and should be really soon now)
Thank you for your work.
-- Leon
On 11/06/2020 15:30, Leon Fauster via CentOS-devel wrote:
Am 10.06.20 um 22:49 schrieb Fabian Arrotin:
<snip>
Can I use this ks file to compose an new image with lorax? Or are some other tools missing / unseen by me to build a working image?
You can use virt-install, or lorax or any other tool (but you'll probably need some url / repo lines added) to build an image from this https://git.centos.org/centos/kickstarts/blob/master/f/CentOS-8-EC2.ks file
The authoritative builds on koji/mbox (like for example this one : https://koji.mbox.centos.org/koji/buildinfo?buildID=11432) is using pungi and so these configs (also public) : https://git.centos.org/centos/pungi-centos/blob/centos-8.2.2004/f/images-clo...
I would like to start right away booting some instances for testing proposes.
BTW, in the meanwhile I was already elaborating the workflow of importing images into my aws account. thereby i noticed that ec2 import-snapshot does not support the qcow2 disk format. The next supported format would be "raw" ... still elaborating the workflow ...
Yeah, by default we have .qcow2 images as artifacts from the buildsystem, but this morning I tested our 8.2.2004 images (from above koji build link I pasted above) and they worked. We just have to convert to .raw format with qemu-img convert first, before uploading to S3, creating AMI from imported "snapshot"
I tested both x86_64 and aarch64 images and they booted fine (fwiw)
Now to see how to share these AMIs at release/GA time, etc ... :-)
Am 11.06.20 um 16:03 schrieb Fabian Arrotin:
You can use virt-install, or lorax or any other tool (but you'll probably need some url / repo lines added) to build an image from this https://git.centos.org/centos/kickstarts/blob/master/f/CentOS-8-EC2.ks file
The authoritative builds on koji/mbox (like for example this one : https://koji.mbox.centos.org/koji/buildinfo?buildID=11432) is using pungi and so these configs (also public) : https://git.centos.org/centos/pungi-centos/blob/centos-8.2.2004/f/images-clo...
Thanks for the overview!
I build an image based 8.1.1911 (via virt-install) and got it booted on AWS. I noticed while updating the system that dracut has a problem with the injected config in /etc/dracut.conf.d/sgdisk.conf (via CentOS-8-EC2.ks):
... Running scriptlet: glibc-all-langpacks-2.28-72.el8_1.1.x86_64 159/159 Running scriptlet: sssd-common-2.2.0-19.el8_1.1.x86_64 159/159 Running scriptlet: kernel-core-4.18.0-147.8.1.el8_1.x86_64 159/159
dracut-install: ERROR: installing 'sgdisk' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.2koCGr/initramfs -a sgdisk dracut-install: ERROR: installing 'sgdisk' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.VAhgEc/initramfs -a sgdisk
Running scriptlet: microcode_ctl-4:20190618-1.20191115.3.el8_1.x86_64 159/159
dracut-install: ERROR: installing 'sgdisk' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.skbKmv/initramfs -a sgdisk
Running scriptlet: tuned-2.12.0-3.el8_1.1.noarch 159/159 Running scriptlet: glibc-all-langpacks-2.28-72.el8.x86_64 159/159 Running scriptlet: glibc-common-2.28-72.el8_1.1.x86_64
...
Does this problem persists in 8.2.2004 ?
<snip>
I tested both x86_64 and aarch64 images and they booted fine (fwiw) Now to see how to share these AMIs at release/GA time, etc ... :-)
Sounds great!
-- Leon
Am 12.06.20 um 22:21 schrieb Leon Fauster:
I build an image based 8.1.1911 (via virt-install) and got it booted on AWS. I noticed while updating the system that dracut has a problem with the injected config in /etc/dracut.conf.d/sgdisk.conf (via CentOS-8-EC2.ks):
... Running scriptlet: glibc-all-langpacks-2.28-72.el8_1.1.x86_64 159/159 Running scriptlet: sssd-common-2.2.0-19.el8_1.1.x86_64 159/159 Running scriptlet: kernel-core-4.18.0-147.8.1.el8_1.x86_64 159/159
dracut-install: ERROR: installing 'sgdisk' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.2koCGr/initramfs -a sgdisk dracut-install: ERROR: installing 'sgdisk' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.VAhgEc/initramfs -a sgdisk
Running scriptlet: microcode_ctl-4:20190618-1.20191115.3.el8_1.x86_64 159/159
dracut-install: ERROR: installing 'sgdisk' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.skbKmv/initramfs -a sgdisk
Running scriptlet: tuned-2.12.0-3.el8_1.1.noarch 159/159 Running scriptlet: glibc-all-langpacks-2.28-72.el8.x86_64 159/159 Running scriptlet: glibc-common-2.28-72.el8_1.1.x86_64 ...
Does this problem persists in 8.2.2004 ?
Okay I got it. It seems to happen because gdisk rpm is missed.
Maybe a good idea to update CentOS-8-EC2.ks to install gdisk ahead ...
-- Leon
Hi Akshay
Akshay Kumar writes:
I moved to image builder a while go to get out of the image publishing delays so this doesn't affect me at all. Fabian mentioned not being able to get a hold of anyone in marketplace. I can help with that so if that's a sticking point why not let someone else take a crack at it.
We have a team at Amazon who is actively engaged with KB, Leigh, Fabian and the gang. There is no barrier to publication that comes from the AWS Marketplace. There is a sponsored account for Marketplace and AMI delivery to which at least one of the members of the CentOS team can publish at any time they find appropriate.
There were some delays in the processes for building for the latest arm64 requiring specific patches be brought in upstream from the CentOS project. Those are mostly addressed in RHEL now, but in building your own images, you can look for the specific changes in support of those:
https://github.com/aws/aws-graviton-gettting-started/ points out some of the new issues that have been addressed and where we are looking for significant updates in the libraries. The Graviton CPU supports Arm V8.0 and includes support for CRC and crypto extensions.
And then kernel requires a few changes for full support (those are commited to RHEL and should show up in Stream between the 8.2 and 8.3 kernels
commit 18b915ac6b0ac5ba7ded03156860f60a9f16df2b Author: Dominik Brodowski linux@dominikbrodowski.net Date: Tue Oct 29 18:37:52 2019 +0100
efi/random: Treat EFI_RNG_PROTOCOL output as bootloader randomness and at least parts of the following for add_bootloader_randomness():
commit 428826f5358c922dc378830a1717b682c0823160 Author: Hsin-Yi Wang hsinyi@chromium.org Date: Fri Aug 23 14:24:51 2019 +0800
fdt: add support for rng-seed and set RANDOM_TRUST_BOOTLOADER in the def config.
* And don't forget to include the extended NVME timeout for the instances themselves. This is kernel dependent, so the longer, unsigned int is not available until RHEL 8. The values are reviewed here. I looked over your gist and wondered if you were setting this in the composer blueprint.
On Mon, May 25, 2020 at 7:32 AM Karanbir Singh <kbsingh@centos.orgmailto:kbsingh@centos.org> wrote: On 25/05/2020 11:14, Akshay Kumar wrote:
Fabian,
If you could share some details I'd be happy to take a crack at getting someone at AWS Marketplace to take a look.
If you have an AMI there and can import + run, what is the major hurdle to using them ?
ie, why do you need the image in the marketplace from a user standpoint ?
Regards
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-- David Duncan | Working from Austin, TX Partner Solutions Architect. | +1-512-507-9268, +1-423-771-9529 TZ=America/Chicago | He/Him A: The lost context. Q: What makes top-posted replies harder to read than bottom-posted?
Hi David,
io_timeout for nvme is in that gist. It's a uint 7.5 onwards.
Not clear on the second part. Are you saying there are patches in RHEL AMIs that don't exist RHEL 8.2 and therefore aren't in CentOS 8.2? Or are you just pointing out that since there are no CentOS 8.2 AMIs there is some aarch64 support lagging. That's an important distinction.
On Mon, May 25, 2020 at 10:08 AM David Duncan via CentOS-devel < centos-devel@centos.org> wrote:
Hi Akshay
Akshay Kumar writes:
I moved to image builder a while go to get out of the image publishing delays so this doesn't affect me at all. Fabian mentioned not being able to get a hold of anyone in marketplace. I can help with that so if that's a sticking point why not let someone else take a crack at it.
We have a team at Amazon who is actively engaged with KB, Leigh, Fabian and the gang. There is no barrier to publication that comes from the AWS Marketplace. There is a sponsored account for Marketplace and AMI delivery to which at least one of the members of the CentOS team can publish at any time they find appropriate.
There were some delays in the processes for building for the latest arm64 requiring specific patches be brought in upstream from the CentOS project. Those are mostly addressed in RHEL now, but in building your own images, you can look for the specific changes in support of those:
https://github.com/aws/aws-graviton-gettting-started/ points out some of the new issues that have been addressed and where we are looking for significant updates in the libraries. The Graviton CPU supports Arm V8.0 and includes support for CRC and crypto extensions.
And then kernel requires a few changes for full support (those are commited to RHEL and should show up in Stream between the 8.2 and 8.3 kernels
commit 18b915ac6b0ac5ba7ded03156860f60a9f16df2b Author: Dominik Brodowski linux@dominikbrodowski.net Date: Tue Oct 29 18:37:52 2019 +0100
efi/random: Treat EFI_RNG_PROTOCOL output as bootloader randomnessand at least parts of the following for add_bootloader_randomness():
commit 428826f5358c922dc378830a1717b682c0823160 Author: Hsin-Yi Wang hsinyi@chromium.org Date: Fri Aug 23 14:24:51 2019 +0800
fdt: add support for rng-seedand set RANDOM_TRUST_BOOTLOADER in the def config.
- And don't forget to include the extended NVME timeout for the instances themselves. This is kernel dependent, so the longer, unsigned int is not available until RHEL 8. The values are reviewed here. I looked over your gist and wondered if you were setting this in the composer blueprint.
On Mon, May 25, 2020 at 7:32 AM Karanbir Singh <kbsingh@centos.org
mailto:kbsingh@centos.org> wrote:
On 25/05/2020 11:14, Akshay Kumar wrote:
Fabian,
If you could share some details I'd be happy to take a crack at getting someone at AWS Marketplace to take a look.
If you have an AMI there and can import + run, what is the major hurdle to using them ?
ie, why do you need the image in the marketplace from a user standpoint ?
Regards
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-- David Duncan | Working from Austin, TX Partner Solutions Architect. | +1-512-507-9268, +1-423-771-9529 TZ=America/Chicago | He/Him A: The lost context. Q: What makes top-posted replies harder to read than bottom-posted? _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Mon, 2020-05-25 at 11:13 -0400, Akshay Kumar wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Hi David,
io_timeout for nvme is in that gist. It's a uint 7.5 onwards.
Awesome! I missed it.
Not clear on the second part. Are you saying there are patches in RHEL AMIs that don't exist RHEL 8.2 and therefore aren't in CentOS 8.2? Or are you just pointing out that since there are no CentOS 8.2 AMIs there is some aarch64 support lagging. That's an important distinction.
Pointing out that there is a lag in the full support for some of the aarch64 instances coming out currently. IT's going to be a little while before there is full support for them, but the A1 is fully supported with the latest aarch64 images.
On Mon, May 25, 2020 at 10:08 AM David Duncan via CentOS-devel < centos-devel@centos.org> wrote:
Hi Akshay
Akshay Kumar writes:
I moved to image builder a while go to get out of the image
publishing
delays so this doesn't affect me at all. Fabian mentioned not
being
able to get a hold of anyone in marketplace. I can help with that
so
if that's a sticking point why not let someone else take a crack
at
it.
We have a team at Amazon who is actively engaged with KB, Leigh, Fabian and the gang. There is no barrier to publication that comes from the AWS Marketplace. There is a sponsored account for Marketplace and AMI delivery to which at least one of the members of the CentOS team can publish at any time they find appropriate.
There were some delays in the processes for building for the latest arm64 requiring specific patches be brought in upstream from the CentOS project. Those are mostly addressed in RHEL now, but in building your own images, you can look for the specific changes in support of those:
https://github.com/aws/aws-graviton-gettting-started/ points out some of the new issues that have been addressed and where we are looking for significant updates in the libraries. The Graviton CPU supports Arm V8.0 and includes support for CRC and crypto extensions.
And then kernel requires a few changes for full support (those are commited to RHEL and should show up in Stream between the 8.2 and 8.3 kernels
commit 18b915ac6b0ac5ba7ded03156860f60a9f16df2b Author: Dominik Brodowski linux@dominikbrodowski.net Date: Tue Oct 29 18:37:52 2019 +0100
efi/random: Treat EFI_RNG_PROTOCOL output as bootloaderrandomness and at least parts of the following for add_bootloader_randomness():
commit 428826f5358c922dc378830a1717b682c0823160 Author: Hsin-Yi Wang hsinyi@chromium.org Date: Fri Aug 23 14:24:51 2019 +0800
fdt: add support for rng-seedand set RANDOM_TRUST_BOOTLOADER in the def config.
- And don't forget to include the extended NVME timeout for the instances themselves. This is kernel dependent, so the longer, unsigned int is not available until RHEL 8. The values are
reviewed here. I looked over your gist and wondered if you were setting this in the composer blueprint.
On Mon, May 25, 2020 at 7:32 AM Karanbir Singh <
kbsingh@centos.orgmailto:kbsingh@centos.org> wrote:
On 25/05/2020 11:14, Akshay Kumar wrote:
Fabian,
If you could share some details I'd be happy to take a crack at
getting
someone at AWS Marketplace to take a look.
If you have an AMI there and can import + run, what is the major
hurdle
to using them ?
ie, why do you need the image in the marketplace from a user
standpoint ?
Regards
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-- David Duncan | Working from Austin, TX Partner Solutions Architect. | +1-512-507-9268, +1-423-771- 9529 TZ=America/Chicago | He/Him A: The lost context. Q: What makes top-posted replies harder to read than bottom-posted? _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Akshay Kumar -
Alan Ivey -
David Duncan -
Duncan, David
-
Fabian Arrotin -
Greg Bailey -
Karanbir Singh -
Leon Fauster -
Marcin Dulak -
Nico Kadel-Garcia -
Thomas Stephen Lee