Open Stack

The problem with the other projects image builds is that they are
based for bigger systems, while cirros is an embedded-device-like
image which boots in a couple of seconds.

Couldn't we contribute to cirros to have such module load by default [1]?

Or may be it's time for Openstack to build their own "cirros-like"
image with all the capabilities we may be missing for general tempest
testing? (ipv6, vlan, etc..? )


[1] http://bazaar.launchpad.net/~cirros-dev/cirros/trunk/view/head:/bin/grab-kernels

On Sat, Aug 6, 2016 at 11:15 PM, Jeremy Stanley <fungi at yuggoth.org> wrote:
> On 2016-08-06 14:44:27 -0600 (-0600), Doug Wiegley wrote:
>> I would be tempted to make a custom image, and ask to put it on
>> our mirrors, or have nodepool manage the image building and
>> storing.
>
> Some projects (I think at least Ironic and Trove) have CI jobs to
> build custom virtual machine images they then boot under nova in
> DevStack using jobs. At the moment the image build jobs are
> uploading to tarballs.openstack.org and then test jobs are consuming
> them from there.
>
>> You can also likely just have the module on the local mirrors,
>> which would alleviate the random internet issue.
> [...]
>
> We've discussed this, and I think it makes sense. If we move our
> tarballs site into AFS, then we could serve its contents from our
> local AFS cache mirrors in each provider for improved performance.
> This may not work well for exceptionally large images due to the
> time it takes to pull them into the AFS cache over the Internet, but
> some experimentation with small and infrequently-updated custom disk
> images seems like it could prove worthwhile.
> --
> Jeremy Stanley
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev