Re: [openstack-dev] [TripleO][DIB] how create triplo overcloud image with latest kernel?
I've used the following trick in the past to enlarge the images:
qemu-img resize ${OVERCLOUD_IMG} +3G
LIBGUESTFS_BACKEND=direct virt-customize -m 2048 -a
${OVERCLOUD_IMG} --run-command 'xfs_growfs /dev/sda'
Please also double-check the filesystem, some overcloud images use
ext4, for example. After modifying the image, I then run virt-sparsify
to shrink them a bit.
On Tue, Sep 26, 2017 at 12:43 PM, Moshe Levi <mosh...@mellanox.com> wrote:
> Hi all,
>
>
>
> As part of the OVS Hardware Offload [1] [2], we need to create new
> Centos/Redhat 7 image with latest kernel/ovs/iproute.
>
> We tried to use virsh-customize to install the packages and we were able to
> update iproute and ovs, but for the kernel there is no space.
>
> We also tried with virsh-customize to uninstall the old kenrel but we no
> luck.
>
> Is other ways to replace kernel package in existing image?
>
>
>
>
>
>
>
> [1] - https://review.openstack.org/#/c/504911/
>
> [2] - https://review.openstack.org/#/c/502313/
>
>
>
>
>
>
> __
> 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
>
--
Jan Gutter
Embedded Networking Software Engineer
Netronome | First Floor Suite 1, Block A, Southdowns Ridge Office Park,
Cnr Nellmapius and John Vorster St, Irene, Pretoria, 0157
Phone: +27 (12) 665-4427 | Skype: jangutter | www.netronome.com
__
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] os-vif 1.6.1 release for pike.
On Tue, Jul 18, 2017 at 5:54 PM, Mooney, Sean K <sean.k.moo...@intel.com> wrote: > Should have: > > Improve OVS Representor Lookup https://review.openstack.org/#/c/484051/ I've split out the review into two portions, here is the second one: Improve OVS Representor VF Lookup https://review.openstack.org/#/c/485125/ -- Jan Gutter Embedded Networking Software Engineer Netronome | First Floor Suite 1, Block A, Southdowns Ridge Office Park, Cnr Nellmapius and John Vorster St, Irene, Pretoria, 0157 Phone: +27 (12) 665-4427 | Skype: jangutter | www.netronome.com __ 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] [nova] Contributing support for Netronome Agilio adaptors
Hi, Apologies for leaving this to the very last minute. The blueprint and spec has been submitted for your consideration to: https://blueprints.launchpad.net/nova/+spec/netronome-smartnic-enablement https://review.openstack.org/#/c/456386/ We're in the final steps of getting the permission to share the example code, but it might not make it in time for tomorrow. Please feel free to email me for any questions: I'll try to be on IRC tomorrow (my timezone is GMT+02:00). -- Jan Gutter Embedded Networking Software Engineer Netronome | First Floor Suite 1, Block A, Southdowns Ridge Office Park, Cnr Nellmapius and John Vorster St, Irene, Pretoria, 0157 Phone: +27 (12) 665-4427 | Skype: jangutter | www.netronome.com __ 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] [nova] Contributing support for Netronome Agilio adaptors
Greetings, Apologies for chiming in very late into the spec cycle. Netronome is completing its internal processes in order to allow developers to contribute code to OpenStack and we should be able to share patches within the week. Additional apologies for the long wall of text that's following. We would really like to upstream support for our NICs in Pike. We've got patches that hook into core Nova (and make a tiny modification to the Neutron ML2 OVS mechanism plugin) to allow VM's to be plugged into our NIC's accelerated ports. The mechanism that we chose was to add another set of VNIC types (in the same group where VNIC_TYPE_NORMAL and VNIC_TYPE_DIRECT are defined), for the two separate plugging methods that we support. It's also very possible for us to just add one more (VNIC_TYPE_RELAY) and have everything work for us. (we also considered flavor and glance annotations, but chose this method for flexibility) We have two methods to plug VMs into the bridge. On Nova's side, they look either like vhost-user, or SR-IOV passthrough. On Neutron's side, everything look like an OVS bridge. Crucially, we support all three methods (standard TAP, SR-IOV and vhost-user) on the _same_ bridge, with SR-IOV and vhost-user accelerated, and with everything except SR-IOV being live-migrateable. I'm hoping that, by tomorrow, we'll have the necessary internal permissions in place to start discussing code. We'd appreciate any advice on processes and protocol to follow. Would it still be possible to jump on the Pike release? There is absolutely no emotional attachment to this code, so if a major redesign is on the cards, we'd be very agreeable to do so. Thanks again very much for reading this sizeable missive. I hope we can get on board and start contributing to OpenStack as soon as possible. (There's a lot of automatic tuning, pinning and scheduling support bits we'd like to contribute as well.) -- Jan Gutter Embedded Networking Software Engineer Netronome | First Floor Suite 1, Block A, Southdowns Ridge Office Park, Cnr Nellmapius and John Vorster St, Irene, Pretoria, 0157 Phone: +27 (12) 665-4427 | Skype: jangutter | www.netronome.com __ 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
