Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Scott Moser]

On Mon, 8 Aug 2016, Jeremy Stanley wrote:

> On 2016-08-08 11:20:54 +0200 (+0200), Miguel Angel Ajo Pelayo wrote:
> > 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.
>
> Yep, smaller is certainly better when it comes to trying to run Nova
> in a virtual machine.
>
> > Couldn't we contribute to cirros to have such module load by default [1]?
>
> It's worth chatting with them, for sure, and see what they say about
> it.
>

Kevin opened a bug at
 https://bugs.launchpad.net/cirros/+bug/1605832
I responded with a one option that we could pursue to avoid others having
to build their own images.
The suggestion was to provide a command line utility in inside cirros that
would download additional kernel modules.  Then, user-data could be fed to
instruct it to do so.  That would allow you to keep using unmodified
cirros kernels and initramfs.

Another option would be for cirros to provide other ways to patch itself
to your needs.  For example, the injected files support in nova could be
used to insert the necessary modules.  The difficulty there is that then
you're dependent upon knowing what version of the kernel is inside the
image.

Another option is for cirros to simply include those modules by default.
That comes at the cost of 100k or so.  Its not a huge thing, but its
definitely an increase.

We can work something out.

Scott

> > 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..? )
>
> I haven't personally tested the CirrOS build instructions, but have
> a feeling writing a diskimage-builder element wrapper for that
> wouldn't be particularly challenging.



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Miguel Angel Ajo Pelayo]

Answers inline.

On Tue, Aug 9, 2016 at 8:08 AM, Antonio Ojea  wrote:
> What do you think about openwrt images?
>
> They are small, have documentation to build your custom images, have a
> packaging system and have tons of networking features (ipv6, vlans, ...) ,
> also seems that someone has done the work to adapt to openstack [1]
>
>
> [1] http://hackstack.org/x/blog/2014/08/17/openwrt-images-for-openstack/
>

At first glance, that could be a good idea, openwrt is low in memory
footprint, and high on network capabilities (which could be a good
thing for testing)

For example, having things like netperf/iperf could be a great thing
for tools likes shaker or bandwidth shaping policing tests.



>
> On Tue, Aug 9, 2016 at 1:56 AM, Ian Wienand  wrote:
>>
>> On 08/09/2016 02:10 AM, Jeremy Stanley wrote:
>>>
>>> I haven't personally tested the CirrOS build instructions, but have
>>> a feeling writing a diskimage-builder element wrapper for that
>>> wouldn't be particularly challenging.
>>
>>
>> I'm not exactly sure it fits that well into dib; it seems like
>> "bundle" has it mostly figured out.  I say that based on [1] where we
>> are discussing a similar thing for cirros images with watchdog
>> support.
>>
>> As mentioned we can easily build these and store them, and put them on
>> mirrors if we need them closer to nodes.  What I mentioned in [1] and
>> didn't particularly like is if the build of these images is totally
>> removed from where they're actually used (e.g. a custom script inside
>> a job in project-config, where basically anyone outside infra can't
>> easily replicate the build for a local test).  But if several projects
>> are building slightly different cusomised cirros images, it might be
>> worth consolidating.
>>

I agree with Ian here, we should be in control of how tiny test images
are built, so probably a project & tuneable job to build those images
would be a fantastic idea IMO, if that's what you mean.


>> -i
>>
>> [1]
>> https://review.openstack.org/#/c/338167/2/tools/build-watchdog-images.sh
>>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Antonio Ojea]

What do you think about openwrt images?

They are small, have documentation to build your custom images, have a
packaging system and have tons of networking features (ipv6, vlans, ...) ,
also seems that someone has done the work to adapt to openstack [1]


[1] http://hackstack.org/x/blog/2014/08/17/openwrt-images-for-openstack/


On Tue, Aug 9, 2016 at 1:56 AM, Ian Wienand  wrote:

> On 08/09/2016 02:10 AM, Jeremy Stanley wrote:
>
>> I haven't personally tested the CirrOS build instructions, but have
>> a feeling writing a diskimage-builder element wrapper for that
>> wouldn't be particularly challenging.
>>
>
> I'm not exactly sure it fits that well into dib; it seems like
> "bundle" has it mostly figured out.  I say that based on [1] where we
> are discussing a similar thing for cirros images with watchdog
> support.
>
> As mentioned we can easily build these and store them, and put them on
> mirrors if we need them closer to nodes.  What I mentioned in [1] and
> didn't particularly like is if the build of these images is totally
> removed from where they're actually used (e.g. a custom script inside
> a job in project-config, where basically anyone outside infra can't
> easily replicate the build for a local test).  But if several projects
> are building slightly different cusomised cirros images, it might be
> worth consolidating.
>
> -i
>
> [1] https://review.openstack.org/#/c/338167/2/tools/build-watchd
> og-images.sh
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Ian Wienand]

On 08/09/2016 02:10 AM, Jeremy Stanley wrote:

I haven't personally tested the CirrOS build instructions, but have
a feeling writing a diskimage-builder element wrapper for that
wouldn't be particularly challenging.


I'm not exactly sure it fits that well into dib; it seems like
"bundle" has it mostly figured out.  I say that based on [1] where we
are discussing a similar thing for cirros images with watchdog
support.

As mentioned we can easily build these and store them, and put them on
mirrors if we need them closer to nodes.  What I mentioned in [1] and
didn't particularly like is if the build of these images is totally
removed from where they're actually used (e.g. a custom script inside
a job in project-config, where basically anyone outside infra can't
easily replicate the build for a local test).  But if several projects
are building slightly different cusomised cirros images, it might be
worth consolidating.

-i

[1] https://review.openstack.org/#/c/338167/2/tools/build-watchdog-images.sh


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Jeremy Stanley]

On 2016-08-08 11:20:54 +0200 (+0200), Miguel Angel Ajo Pelayo wrote:
> 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.

Yep, smaller is certainly better when it comes to trying to run Nova
in a virtual machine.

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

It's worth chatting with them, for sure, and see what they say about
it.

> 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..? )

I haven't personally tested the CirrOS build instructions, but have
a feeling writing a diskimage-builder element wrapper for that
wouldn't be particularly challenging.
-- 
Jeremy Stanley

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Miguel Angel Ajo Pelayo]

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  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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Jeremy Stanley]

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Doug Wiegley]

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.

You can also likely just have the module on the local mirrors, which would 
alleviate the random internet issue. 

Bigger OS'es with nested Virt is kinda pain. 

Doug


> On Aug 5, 2016, at 3:37 PM, Kevin Benton  wrote:
> 
> Hi,
> 
> In neutron there is a new feature under active development to allow a VM to 
> attach to many networks via its single interface using VLAN tags.
> 
> We would like this to be tested in a scenario test in the gate, but in order 
> to do that the guest instance must have support for VLAN tags (the 8021q 
> kernel module for Linux VMs). Cirros does not ship with this module so I have 
> a few questions.
> 
> Do any other projects need to load a kernel module for a specific test? If 
> not, where would the best place be to store the module so we can load it for 
> that test; or, should we download it directly from the Internet (worried 
> about the stability of this)?
> 
> Thanks, 
> Kevin Benton
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Mooney, Sean K]

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Friday, August 5, 2016 10:37 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [infra][neutron] - best way to load 8021q kernel 
module into cirros


Hi,

In neutron there is a new feature under active development to allow a VM to 
attach to many networks via its single interface using VLAN tags.
 [Mooney, Sean K] In this case I take it that you want to create a scenario 
test that will cover teh vlan aware vms work is that correct?

We would like this to be tested in a scenario test in the gate, but in order to 
do that the guest instance must have support for VLAN tags (the 8021q kernel 
module for Linux VMs). Cirros does not ship with this module so I have a few 
questions.
[Mooney, Sean K] Is there a reason you cannot use a Ubuntu or centos cloud 
image for the guest for this test?
both would require the vm flavor to have at least 256mb of ram but I think that 
should be fine.

Do any other projects need to load a kernel module for a specific test? If not, 
where would the best place be to store the module so we can load it for that 
test; or, should we download it directly from the Internet (worried about the 
stability of this)?
[Mooney, Sean K]  how big is it? Would it fit on a configdrive/retrieve it via 
the metatdata service.
looking at https://bugs.launchpad.net/cirros/+bug/1605832 they are suggesting 
using or add a get-kernel-module command but if it was small
you could just store it in the metatdata service/config drive or even swift and 
just curl it locally and run insmod to insert it.





Thanks,
Kevin Benton
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

[Kevin Benton]

Hi,

In neutron there is a new feature under active development to allow a VM to
attach to many networks via its single interface using VLAN tags.

We would like this to be tested in a scenario test in the gate, but in
order to do that the guest instance must have support for VLAN tags (the
8021q kernel module for Linux VMs). Cirros does not ship with this module
so I have a few questions.

Do any other projects need to load a kernel module for a specific test? If
not, where would the best place be to store the module so we can load it
for that test; or, should we download it directly from the Internet
(worried about the stability of this)?

Thanks,
Kevin Benton
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev