Fresh AMIs (official Fedora acct, min vol size)

[David Gay]

Hello, cloud friends.

I've attached a signed list of fresh AMIs for the images we provide through [1]. If no one sees any problems here, we could ask someone from the web team to update that page with these new AMIs.

Notables:

- These AMIs were registered on the *official* Fedora AWS account, to which few people (to my knowledge) have access
  - The AMIs currently listed on [1] were registered with the less-locked-down community cloud account

- AMI volume sizes are now "tailored to fit", to reduce AWS costs
  - Base images use 3 GB volumes (our minimum)
  - Atomic images use 7 GB volumes (uncompressed Atomic images are about 6.1 GB)

- Fedimg jobs were triggered on the fedimg01 machine, so there's a trail of fedmsgs like [2]

[1]: https://getfedora.org/en/cloud/download/
[2]: https://apps.fedoraproject.org/datagrepper/id?id=2015-d218ae58-ce79-46d8-9c6...

-- David

[Dusty Mabe]

On Mon, Feb 02, 2015 at 11:00:27PM -0500, David Gay wrote:
> Hello, cloud friends.
>
> I've attached a signed list of fresh AMIs for the images we provide through [1]. If no one sees any problems here, we could ask someone from the web team to update that page with these new AMIs.
>
> Notables:
> These AMIs were registered on the *official* Fedora AWS account, to which few people (to my knowledge) have access
> The AMIs currently listed on [1] were registered with the less-locked-down community cloud account

A few questions/comments:

- Do these images include updates? I think our AMI release cadence should 
  mirror our release schedule for the xz/qcow2 images.
- The image that shows up for US East (N. Virginia) when you click on Base 
  Cloud is ami-164cd77e but the launch hyperlink [1] points to ami-fa3dbf92.

[1] - https://redirect.fedoraproject.org/console.aws.amazon.com/ec2/v2/home?region...

[David Gay]

----- Original Message -----
> From: "Dusty Mabe" 
> To: [e-mail]
> Sent: Tuesday, February 3, 2015 7:19:09 AM
> Subject: Re: Fresh AMIs (official Fedora acct, min vol size)
>
> On Mon, Feb 02, 2015 at 11:00:27PM -0500, David Gay wrote:
> > Hello, cloud friends.
> >
> > I've attached a signed list of fresh AMIs for the images we provide through
> > [1]. If no one sees any problems here, we could ask someone from the web
> > team to update that page with these new AMIs.

[snip]
> A few questions/comments:
> Do these images include updates? I think our AMI release cadence should
> mirror our release schedule for the xz/qcow2 images.

These AMIs were created from the images we provide at [1]. Specifically, [2] and [3]. Whatever's in those images is what's in these AMIs. Is there another image they should have been built from? If so, I'm missing something. My understanding is that a new image build would have shown up in Koji. That's what triggers Fedimg. Apparently, there hasn't been a successful createImage task in weeks[4].

[1]: https://getfedora.org/en/cloud/download/#Amazon%20Public%20Cloud%20EC2%20Ima...
[2]: http://download.fedoraproject.org/pub/fedora/linux/releases/21/Cloud/Images/...
[3]: http://download.fedoraproject.org/pub/fedora/linux/releases/21/Cloud/Images/...
[4]: http://koji.fedoraproject.org/koji/tasks?state=all&view=flat&method=...

-- David

[Matthew Miller]

On Tue, Feb 03, 2015 at 04:38:11PM -0500, David Gay wrote:
> These AMIs were created from the images we provide at [1]. Specifically, [2] and [3]. Whatever's in those images is what's in these AMIs. Is there another image they should have been built from? If so, I'm missing something. My understanding is that a new image build would have shown up in Koji. That's what triggers Fedimg. Apparently, there hasn't been a successful createImage task in weeks[4].
> [1]: https://getfedora.org/en/cloud/download/#Amazon%20Public%20Cloud%20EC2%20Ima...

Yeah, we're still at planning stage for actually doing updated images
regularly....

[Matthew Miller]

On Tue, Feb 03, 2015 at 04:38:11PM -0500, David Gay wrote:
> Apparently, there hasn't been a successful createImage task in weeks[4].
> [4]: http://koji.fedoraproject.org/koji/tasks?state=all&view=flat&method=...

libvirt not running on builders?

Exception encountered in _build_image_from_template thread
Cannot connect to libvirt.  Make sure libvirt is running. [Original
message: Failed to connect socket to '/var/run/libvirt/libvirt-sock':
No such file or directory]
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/imgfac/Builder.py", line 132,
in _build_image_from_template
    self.os_plugin.create_base_image(self, template, parameters)
  File
"/usr/lib/python2.7/site-packages/imagefactory_plugins/TinMan/TinMan.py",
line 322, in create_base_image
    self._init_oz()
  File
"/usr/lib/python2.7/site-packages/imagefactory_plugins/TinMan/TinMan.py",
line 299, in _init_oz
    self.init_guest()
  File
"/usr/lib/python2.7/site-packages/imagefactory_plugins/TinMan/TinMan.py",
line 407, in init_guest
    raise ImageFactoryException("Cannot connect to libvirt.  Make sure
libvirt is running. [Original message: %s]" %  e.message)
ImageFactoryException: Cannot connect to libvirt.  Make sure libvirt is
running. [Original message: Failed to connect socket to
'/var/run/libvirt/libvirt-sock': No such file or directory]
ABORT called in TinMan plugin
No Oz guest object present - nothing to do