TipsAndTricks/Running YP Image On AWS - Revision history

Amber Elliot: /* Build Yocto image */

2017-11-16T18:55:01Z

Build Yocto image

← Older revision		Revision as of 18:55, 16 November 2017
Line 23:		Line 23:
	grub \		grub \
	connman \		connman \
	kernel-module-xen-acpi-processor \		kernel-module-xen-acpi-processor \

	IMAGE_FEATURES += " ssh-server-openssh"		IMAGE_FEATURES += " ssh-server-openssh"
	<nowiki> # Ensure extra space for guest images </nowiki>		<nowiki># Ensure extra space for guest images </nowiki>
	IMAGE_ROOTFS_EXTRA_SPACE = "1000000"		IMAGE_ROOTFS_EXTRA_SPACE = "1000000"
	DISTRO_FEATURES_append = " systemd virtualization xen "		DISTRO_FEATURES_append = " systemd virtualization xen "
Line 46:		Line 47:
	/workdir/meta-virtualization \		/workdir/meta-virtualization \
	/workdir/meta-cloud-services/meta-openstack \		/workdir/meta-cloud-services/meta-openstack \
	"		"

	##Location of layers can be found from http://layers.openembedded.org		##Location of layers can be found from http://layers.openembedded.org

Amber Elliot: /* Creating an AMI from a Yocto Image */

2017-11-16T18:50:56Z

Creating an AMI from a Yocto Image

← Older revision		Revision as of 18:50, 16 November 2017
Line 9:		Line 9:
	##AWS support claims that grub legacy is required; we suspect this is for licensing reasons. Due to grub 0.97 issues installing onto loopback devices, we failed to get grub legacy up and running on our image, but we were able to get grub 2 booting just fine on AWS. Future work would involve finding a way to use grub 0.97 since that’s what AWS is specifically wanting.		##AWS support claims that grub legacy is required; we suspect this is for licensing reasons. Due to grub 0.97 issues installing onto loopback devices, we failed to get grub legacy up and running on our image, but we were able to get grub 2 booting just fine on AWS. Future work would involve finding a way to use grub 0.97 since that’s what AWS is specifically wanting.
	#Cloud-init		#Cloud-init
	##AWS claims to have a specific cloud-init package, though it seems likely that an up to date package would probably work. Future work would include closely examining running AMIs to determine cloud-init versioning and functionality, and ensure that Yocto layer that supplies cloud-init is providing the proper version ~~(it is currently quite out of date)~~.		##AWS claims to have a specific cloud-init package, though it seems likely that an up to date package would probably work. Future work would include closely examining running AMIs to determine cloud-init versioning and functionality, and ensure that Yocto layer that supplies cloud-init is providing the proper version.

	== Procedure to Build, Upload, and Register the AMI ==		== Procedure to Build, Upload, and Register the AMI ==

Amber Elliot: /* Creating an AMI from a Yocto Image */

2017-11-16T18:50:30Z

Creating an AMI from a Yocto Image

← Older revision		Revision as of 18:50, 16 November 2017
Line 3:		Line 3:

	=== Creating an AMI from a Yocto Image ===		=== Creating an AMI from a Yocto Image ===


	While it is no longer well documented, AWS does still allow custom built linux AMI images so long as they have the following requirements:		While it is no longer well documented, AWS does still allow custom built linux AMI images so long as they have the following requirements:
Line 10:		Line 9:
	##AWS support claims that grub legacy is required; we suspect this is for licensing reasons. Due to grub 0.97 issues installing onto loopback devices, we failed to get grub legacy up and running on our image, but we were able to get grub 2 booting just fine on AWS. Future work would involve finding a way to use grub 0.97 since that’s what AWS is specifically wanting.		##AWS support claims that grub legacy is required; we suspect this is for licensing reasons. Due to grub 0.97 issues installing onto loopback devices, we failed to get grub legacy up and running on our image, but we were able to get grub 2 booting just fine on AWS. Future work would involve finding a way to use grub 0.97 since that’s what AWS is specifically wanting.
	#Cloud-init		#Cloud-init
	##AWS claims to have a specific cloud-init package, though it seems likely that an up to date package would probably work. Future work would include closely examining running AMIs to determine cloud-init versioning and functionality, and ensure that Yocto layer that supplies cloud-init is providing the proper version (it is currently quite out of date).		##AWS claims to have a specific cloud-init package, though it seems likely that an up to date package would probably work. Future work would include closely examining running AMIs to determine cloud-init versioning and functionality, and ensure that Yocto layer that supplies cloud-init is providing the proper version (it is currently quite out of date).




	== Procedure to Build, Upload, and Register the AMI ==		== Procedure to Build, Upload, and Register the AMI ==

Amber Elliot: /* Build your Yocto image */

2017-11-16T18:50:06Z

Build your Yocto image

← Older revision		Revision as of 18:50, 16 November 2017
Line 17:		Line 17:
	== Procedure to Build, Upload, and Register the AMI ==		== Procedure to Build, Upload, and Register the AMI ==

	===Build ~~your~~ Yocto image===		===Build Yocto image===
	''Note: This was done with Yocto Project version 2.4. ''		''Note: This was done with Yocto Project version 2.4. ''

Amber Elliot: /* 'Build your Yocto image */

2017-11-16T18:49:56Z

'Build your Yocto image

← Older revision		Revision as of 18:49, 16 November 2017
Line 17:		Line 17:
	== Procedure to Build, Upload, and Register the AMI ==		== Procedure to Build, Upload, and Register the AMI ==

	==='Build your Yocto image===		===Build your Yocto image===
	''Note: This was done with Yocto Project version 2.4. ''		''Note: This was done with Yocto Project version 2.4. ''

Amber Elliot: /* Create AMI image */

2017-11-16T18:48:52Z

Create AMI image

← Older revision		Revision as of 18:48, 16 November 2017
Line 59:		Line 59:
	''Note: AWS support claims that grub legacy is required for AMIs, but we found that grub2 worked just fine. We had issues installing grub 0.97 on a loopback device, so we just used grub2. These commands are examples - they were used for Ubuntu development systems. Different systems may have slightly different commands. ''		''Note: AWS support claims that grub legacy is required for AMIs, but we found that grub2 worked just fine. We had issues installing grub 0.97 on a loopback device, so we just used grub2. These commands are examples - they were used for Ubuntu development systems. Different systems may have slightly different commands. ''

	# Create an empty img file of desired total size		Create an empty img file of desired total size
	dd if=/dev/zero of=yoctoami.img bs=1M count=500		dd if=/dev/zero of=yoctoami.img bs=1M count=500
	# Create MBR Partition table and set bootable flag		Create MBR Partition table and set bootable flag
	(echo n; echo p; echo 1; echo; echo; echo a; echo p; echo w) \| fdisk yoctoami.img		(echo n; echo p; echo 1; echo; echo; echo a; echo p; echo w) \| fdisk yoctoami.img
	# Mount to loopback device and create filesystem NOTE: The filesystem is formatted on the PARTITION not the general loopback device.		Mount to loopback device and create filesystem NOTE: The filesystem is formatted on the PARTITION not the general loopback device.
	sudo kpartx -av yoctoami.img		sudo kpartx -av yoctoami.img
	sudo mkfs.ext4 /dev/mapper/loopXp1		sudo mkfs.ext4 /dev/mapper/loopXp1
	#Copy a yocto rootfs onto the ext4 partition we just formatted		Copy a yocto rootfs onto the ext4 partition we just formatted
	sudo mount tmp/deploy/images/genericx86-64/core-image-base.ext4 /mnt/yoctofs		sudo mount tmp/deploy/images/genericx86-64/core-image-base.ext4 /mnt/yoctofs
	sudo mount /dev/mapper/loopXp1 /mnt/yoctoami		sudo mount /dev/mapper/loopXp1 /mnt/yoctoami
	rsync -av /mnt/yoctofs/ /mnt/yoctoami/		rsync -av /mnt/yoctofs/ /mnt/yoctoami/
	#Install grub NOTE: Grub is installed onto the loopback device, NOT the partition		Populate grub.cfg and Install grub
			*NOTE: Grub is installed onto the loopback device, NOT the partition. To obtain PARTUUID: blkid /dev/mapper/loopXp1

	mkdir -p /mnt/yoctoami/boot/grub/		mkdir -p /mnt/yoctoami/boot/grub/
	echo "(hd0) /dev/sda" \| sudo tee /mnt/yoctoami/boot/grub/device.map		echo "(hd0) /dev/sda" \| sudo tee /mnt/yoctoami/boot/grub/device.map
	vi /mnt/yoctoami/boot/grub/grub.cfg		vi /mnt/yoctoami/boot/grub/grub.cfg
	~~##Populate your grub.cfg:~~
	~~###Note: To obtain PARTUUID: blkid /dev/mapper/loopXp1~~		menuentry "Yocto Kernel AWS" {
	menuentry "Yocto Kernel AWS" {
	set root='hd0,msdos1'		set root='hd0,msdos1'
	insmod vga		insmod vga
	insmod gzio		insmod gzio
	linux /boot/bzImage-4.12.12-yocto-standard root=PARTUUID=<partid>		linux /boot/bzImage-4.12.12-yocto-standard root=PARTUUID=<partid>
	}		}
	## sudo grub-install --no-floppy --grub-mkdevicemap=/mnt/yoctoami/boot/grub/device.map --root-directory=/mnt/yoctoami /dev/loopX
	##Unmount filesystems
	~~###Sudo~~ umount /mnt/yoctoami		sudo grub-install --no-floppy --grub-mkdevicemap=/mnt/yoctoami/boot/grub/device.map --root-directory=/mnt/yoctoami /dev/loopX
	~~###Sudo~~ kpartx -dv yoctoami.img
	~~###Sudo~~ umount //mnt/yoctofs		Unmount filesystems
			sudo umount /mnt/yoctoami
			sudo kpartx -dv yoctoami.img
			sudo umount //mnt/yoctofs

	===Prepare AWS Account===		===Prepare AWS Account===

Amber Elliot: /* Create AMI image */

2017-11-16T18:42:06Z

Create AMI image

← Older revision		Revision as of 18:42, 16 November 2017
Line 57:		Line 57:

	===Create AMI image===		===Create AMI image===
	'''Note: AWS support claims that grub legacy is required for AMIs, but we found that grub2 worked just fine. We had issues installing grub 0.97 on a loopback device, so we just used grub2.		''Note: AWS support claims that grub legacy is required for AMIs, but we found that grub2 worked just fine. We had issues installing grub 0.97 on a loopback device, so we just used grub2. These commands are examples - they were used for Ubuntu development systems. Different systems may have slightly different commands. ''
	These commands are examples ~~only~~ - they were used for Ubuntu development systems. Different systems may have slightly different commands. '''

	# Create an empty img file of desired total size		# Create an empty img file of desired total size
Line 83:		Line 82:
	linux /boot/bzImage-4.12.12-yocto-standard root=PARTUUID=<partid>		linux /boot/bzImage-4.12.12-yocto-standard root=PARTUUID=<partid>
	}		}


	## sudo grub-install --no-floppy --grub-mkdevicemap=/mnt/yoctoami/boot/grub/device.map --root-directory=/mnt/yoctoami /dev/loopX		## sudo grub-install --no-floppy --grub-mkdevicemap=/mnt/yoctoami/boot/grub/device.map --root-directory=/mnt/yoctoami /dev/loopX
	##Unmount filesystems		##Unmount filesystems

Amber Elliot: /* Create AMI image */

2017-11-16T18:41:06Z

Create AMI image

← Older revision		Revision as of 18:41, 16 November 2017
Line 61:		Line 61:

	# Create an empty img file of desired total size		# Create an empty img file of desired total size
	##dd if=/dev/zero of=yoctoami.img bs=1M count=500		dd if=/dev/zero of=yoctoami.img bs=1M count=500
	# Create MBR Partition table and set bootable flag		# Create MBR Partition table and set bootable flag
	##(echo n; echo p; echo 1; echo; echo; echo a; echo p; echo w) \| fdisk yoctoami.img		(echo n; echo p; echo 1; echo; echo; echo a; echo p; echo w) \| fdisk yoctoami.img
	# Mount to loopback device and create filesystem NOTE: The filesystem is formatted on the PARTITION not the general loopback device.		# Mount to loopback device and create filesystem NOTE: The filesystem is formatted on the PARTITION not the general loopback device.
	##sudo kpartx -av yoctoami.img		sudo kpartx -av yoctoami.img
	##sudo mkfs.ext4 /dev/mapper/loopXp1		sudo mkfs.ext4 /dev/mapper/loopXp1
	#Copy a yocto rootfs onto the ext4 partition we just formatted		#Copy a yocto rootfs onto the ext4 partition we just formatted
	~~##Sudo~~ mount tmp/deploy/images/genericx86-64/core-image-base.ext4 /mnt/yoctofs		sudo mount tmp/deploy/images/genericx86-64/core-image-base.ext4 /mnt/yoctofs
	~~##Sudo~~ mount /dev/mapper/loopXp1 /mnt/yoctoami		sudo mount /dev/mapper/loopXp1 /mnt/yoctoami
	~~##Rsync~~ -av /mnt/yoctofs/ /mnt/yoctoami/		rsync -av /mnt/yoctofs/ /mnt/yoctoami/
	#~~install~~ grub NOTE: Grub is installed onto the loopback device, NOT the partition		#Install grub NOTE: Grub is installed onto the loopback device, NOT the partition
	~~##Mkdir~~ -p /mnt/yoctoami/boot/grub/		mkdir -p /mnt/yoctoami/boot/grub/
	##echo "(hd0) /dev/sda" \| sudo tee /mnt/yoctoami/boot/grub/device.map		echo "(hd0) /dev/sda" \| sudo tee /mnt/yoctoami/boot/grub/device.map
	##vi /mnt/yoctoami/boot/grub/grub.cfg		vi /mnt/yoctoami/boot/grub/grub.cfg
	###Populate your grub.cfg:		##Populate your grub.cfg:
			###Note: To obtain PARTUUID: blkid /dev/mapper/loopXp1
	menuentry "Yocto Kernel AWS" {		menuentry "Yocto Kernel AWS" {
	set root='hd0,msdos1'		set root='hd0,msdos1'
Line 82:		Line 82:
	insmod gzio		insmod gzio
	linux /boot/bzImage-4.12.12-yocto-standard root=PARTUUID=<partid>		linux /boot/bzImage-4.12.12-yocto-standard root=PARTUUID=<partid>
	}		}

	~~''Note: To obtain PARTUUID: blkid /dev/mapper/loopXp1 ''~~

	## sudo grub-install --no-floppy --grub-mkdevicemap=/mnt/yoctoami/boot/grub/device.map --root-directory=/mnt/yoctoami /dev/loopX		## sudo grub-install --no-floppy --grub-mkdevicemap=/mnt/yoctoami/boot/grub/device.map --root-directory=/mnt/yoctoami /dev/loopX

Amber Elliot: /* Create AMI image */

2017-11-16T18:38:51Z

Create AMI image

← Older revision		Revision as of 18:38, 16 November 2017
Line 84:		Line 84:
	}		}

	'''Note: To obtain PARTUUID: blkid /dev/mapper/loopXp1 '''		''Note: To obtain PARTUUID: blkid /dev/mapper/loopXp1 ''

	## sudo grub-install --no-floppy --grub-mkdevicemap=/mnt/yoctoami/boot/grub/device.map --root-directory=/mnt/yoctoami /dev/loopX		## sudo grub-install --no-floppy --grub-mkdevicemap=/mnt/yoctoami/boot/grub/device.map --root-directory=/mnt/yoctoami /dev/loopX
Line 91:		Line 91:
	###Sudo kpartx -dv yoctoami.img		###Sudo kpartx -dv yoctoami.img
	###Sudo umount //mnt/yoctofs		###Sudo umount //mnt/yoctofs


	===Prepare AWS Account===		===Prepare AWS Account===

Amber Elliot: /* Prepare AWS Account */

2017-11-16T18:38:06Z

Prepare AWS Account

← Older revision		Revision as of 18:38, 16 November 2017
Line 104:		Line 104:
	##Following these guidelines, enter a policy with your proper information:		##Following these guidelines, enter a policy with your proper information:
	{		{
	"Version": "2012-10-17",		"Version": "2012-10-17",
	"Statement": [		"Statement": [
	{		{
	"Sid": "Stmt1508534072338",		"Sid": "Stmt1508534072338",
	"Effect": "Allow",		"Effect": "Allow",
	"Principal": {		"Principal": {
	"AWS": "arn:aws:iam::<accountnumber>:<role>"		"AWS": "arn:aws:iam::<accountnumber>:<role>"
	},		},
	"Action": "s3:*",		"Action": "s3:*",
	"Resource": "arn:aws:s3::<:bucketname>"		"Resource": "arn:aws:s3::<:bucketname>"
	}		}
	]		]
	}		}