November 2020 - openstack-discuss

[ironic] [tripleo] RFC: lzma vs gzip for compressing IPA initramfs
by Dmitry Tantsur 30 Nov '20

30 Nov '20

Hi folks, I've been playing with ways to reduce the size of our IPA images. While package removals can only save us tens of megabytes, switching from gzip to lzma reduces the size by around a third (from 373M to 217M in my testing). What's the caveat? The unpacking time increases VERY substantially. On my nested virt lab the 217M image took around 5 minutes to unpack. I'm not sure how much it will impact real bare metal, please feel free to test https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/764371 and tell me. So, what do you think? Switching to lzma by default will likely affect CI run time (assuming we still have DIB jobs somewhere...) and development environments, but it will also provide a visible reduction in the image size (which benefit all environments). Large TripleO images may particularly benefit from this (but also particularly affected by the unpacking time). Feedback is very welcome. Dmitry -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

7 9

[openstack][neutron]How to establish existing Openstack in a single server to other multiple physical NIC port
by dangerzone ar 30 Nov '20

30 Nov '20

Hi, I have deployed packstack (All-In-One) openstack over single server and that openstack traffic is IN/Out via eth1 of the server and that's the network port configured during the packstack deployment. The server has 4 nic ports and only one (nic1) is used during openstack deployment. The openstack running good and my vm/vnf traffic can in/out via eth1. I would like to know how I can utilize other nic port (2,3,4) in my server so that openstack can leverage that port for my other VM/VNF that instantiate in my openstack. For example from the image attached, I want VM/VNF1 connect to nic2 and VM/VNF2 connect to nic3. Please advise how it can be done. I really hope someone could advise and help me further. Thank you. **This is standard openstack (deployed via packstack all-in-one) over single centos7 server that have 4 nic ports**

2 1

[telemetry] wallaby cycle planning session
by Matthias Runge 30 Nov '20

30 Nov '20

Hi there, one of the biggest challenges for the telemetry stack is currently the state of gnocchi, which is... undefined/unfortunate/under-contributed/...? Telemetry started long time ago as a simple component ceilometer, which was split into several components ceilometer, aodh, panko, and gnocchi. Julien wrote a story about this some time ago[1]. There has also been an attempt to fork gnocchi back to OpenStack[2]. To my knowledge, the original contributors are not paid anymore to work on gnocchi, and at the same time, moving on to do something else is totally fine. However, I am not sure if we (in OpenStack Telemetry) should or could maintain in addition to the rest of the telemetry stack a time-series database. I'd like to discuss this during a call. Please select time(s) that suit you best in this poll[3]. If you have questions or hints, don't hesitate to contact me. Thank you, Matthias [1] https://julien.danjou.info/lessons-from-openstack-telemetry-deflation/ [2] https://review.opendev.org/#/c/744592/ [3] https://doodle.com/poll/uqq328x5shr43awy

5 15

[training-labs] OpenStack training-labs expired link
by Jeremy SNIDARO 29 Nov '20

29 Nov '20

Hello, The scripts to setup the labs (labs-master\labs\osbash\wbatch\create_base.bat) is trying to download an version of ubuntu that is no longer available on the URL : http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.4-server-amd6… The new URL should be : http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.*5* -server-amd64.iso On github it is on the file labs/stacktrain/distros/ubuntu_18_04_server_amd64.py <https://github.com/openstack/training-labs/blob/master/labs/stacktrain/dist…> Regards, ----------------------------------------------------------------- Jérémy SNIDARO GNU/Linux System Administrator - DevOps jeremysnidaro.com - France 86000 Poitiers [image: LinkedIn] <https://www.linkedin.com/in/jeremy-snidaro/>

1 0

[openstack] [InteropWG] Planning Approval by Nov 30th through email and later at Dec 8th Board meeting
by prakash RAMCHANDRAN 28 Nov '20

28 Nov '20

Hi all, Hope you all had a good Thanks Giving and like to proceed from draft guidelines on the VIctoria Interop to Approval at next Board meeting on Dec 8th. https://wiki.openstack.org/wiki/Governance/Foundation/8Dec2020BoardMeeting Please review the draft before Nov 30th Monday noon as we would like this 2020.11.* date maintained and will request an approval by Nov 30th, https://review.opendev.org/c/osf/interop/+/762719 The Interop WG meeting on Dec 3 , we will focus on maintenance of ReftStack and any additional discussions you like to bring for OIF InteropWG wrt add-on modules and or independent k8s conformance for Open Infrastructure Projects. https://etherpad.opendev.org/p/interop ThanksPrakash For InteropWG

1 0

[all][nova][placement] Merging 'placement' IRC channel into 'nova'
by Ghanshyam Mann 28 Nov '20

28 Nov '20

Hello Everyone, As the placement project is under Nova governance now[1], can we merge the IRC channel 'placement' into nova? I think that can be done via redirect way? [1] https://review.opendev.org/c/openstack/governance/+/760917 -gmann

3 2

Re: [neutron][openstack-ansible] Instances can only connect to provider-net via tenant-net but not directly
by Oliver Wenz 27 Nov '20

27 Nov '20

> So this looks like issue during sending notification to Nova. You should check > in Nova logs now why it returned You 422 The relevant nova-compute log on the node where I try to start the instance looks like this: Nov 27 13:33:24 bc1blade15 nova-compute[4240]: 2020-11-27 13:33:24.870 4240 INFO nova.compute.claims [req-4125d882-0753-4a0a-844c-5a948681ffa1 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 - default default] [instance: 20a23a18-0d13-4aba-b0be-37e243b21336] Claim successful on node bc1blade15.openstack.local Nov 27 13:33:26 bc1blade15 nova-compute[4240]: 2020-11-27 13:33:26.151 4240 INFO nova.virt.libvirt.driver [req-4125d882-0753-4a0a-844c-5a948681ffa1 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 - default default] [instance: 20a23a18-0d13-4aba-b0be-37e243b21336] Creating image Nov 27 13:33:31 bc1blade15 nova-compute[4240]: 2020-11-27 13:33:31.463 4240 INFO os_vif [req-4125d882-0753-4a0a-844c-5a948681ffa1 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 - default default] Successfully plugged vif VIFBridge(active=False,address=fa:16:3e:57:d5:f4,bridge_name='brq497a58ad-e5',has_traffic_filtering=True,id=c2e13a92-86bc-4c8e-ad74-1cad0a6bcffc,network=Network(497a58ad-e57c-4bf1-a1c7-dad58f4795ec),plugin='linux_bridge',port_profile=<?>,preserve_on_delete=False,vif_name='tapc2e13a92-86') Nov 27 13:33:33 bc1blade15 nova-compute[4240]: 2020-11-27 13:33:33.961 4240 INFO nova.compute.manager [req-633ff74b-b16d-4063-9f54-5ee618ea2bb9 - - - - -] [instance: 20a23a18-0d13-4aba-b0be-37e243b21336] VM Started (Lifecycle Event) Nov 27 13:33:34 bc1blade15 nova-compute[4240]: 2020-11-27 13:33:34.104 4240 INFO nova.compute.manager [req-633ff74b-b16d-4063-9f54-5ee618ea2bb9 - - - - -] [instance: 20a23a18-0d13-4aba-b0be-37e243b21336] VM Paused (Lifecycle Event) Nov 27 13:33:34 bc1blade15 nova-compute[4240]: 2020-11-27 13:33:34.388 4240 INFO nova.compute.manager [req-633ff74b-b16d-4063-9f54-5ee618ea2bb9 - - - - -] [instance: 20a23a18-0d13-4aba-b0be-37e243b21336] During sync_power_state the instance has a pending task (spawning). Again, the corresponding neutron-server log: Nov 27 13:39:02 infra1-neutron-server-container-cbf4b105 neutron-server[87]: 2020-11-27 13:39:02.106 87 WARNING neutron.notifiers.nova [-] Nova event: {'server_uuid': '20a23a18-0d13-4aba-b0be-37e243b21336', 'name': 'network-vif-deleted', 'tag': 'c2e13a92-86bc-4c8e-ad74-1cad0a6bcffc', 'status': 'failed', 'code': 422} returned with failed status I also looked in all the logs of the nova related services on the managament node for the instance id but didn't find it. So the nova-compute log seems to indicate that the instance can connect to the bridge successfully?!

2 1

Re: [tripleo] Copying tripleo container images to quay.io
by Bogdan Dobrelya 27 Nov '20

27 Nov '20

So I explored how exactly skopeo copy works with the WIP zstd:chunked compression format. The main case here is when copying *new* layers of the *same* image. What is not the case in TripleO CI. We build images from scratch and tag it only once, like current-tripleo. Here ends that build's lifecycle. Had we decided to change that to update existing images, we could come back and try that new feature of skopeo, or may be even consume it directly via buildah bud, when it's there. Another caveat is that only OCI compliant registries could accept such zstd:chunked compressed layers. But anyway that was a good try... Bogdan Dobrelya bdobreli at redhat.com writes: > Note that skopeo will shortly have the layers diffs [0] based "copy" > operations [1],[2],[3]. It also deduplicates things and uses local cache > to not repeat redundant data transfers. Would be great if TripleO > container registry could start using that super cool feature as early > adoption. > > We could make a build with these patches and try that for the subject > tooling for TCIB distribution over quay.io. > > IIUC, the process is like: > > * as input we have full layers from the source registry, built with TCIB; > * skopeo uses its super powers to redo it on fly into layers diff > * either skopeo as well, or maybe even tripleoclient prepare image CLI > pushes those optimized layers of the images to the target quay.io registry. > * ??? > * profit! > > [0] https://github.com/containers/image/pull/902 > [1] https://github.com/containers/image/pull/1084 > [2] https://github.com/containers/storage/pull/775 > [3] https://github.com/containers/skopeo/pull/1111 -- Best regards, Bogdan Dobrelya, Irc #bogdando

1 0

[tripleo] Please avoid merge patches for releases before Victoria
by Arx Cruz 27 Nov '20

27 Nov '20

Hello, We need these patches [1] landed first in order to merge other patches, otherwise CI will not be able to properly test it. We have already had two known issues [2] related to this problem, so I ask you for patience while we are merging those patches. [1] https://review.opendev.org/c/openstack/tripleo-quickstart/+/763747 https://review.opendev.org/#/c/763712 [2] https://launchpad.net/bugs/1903033 https://bugs.launchpad.net/tripleo/+bug/1905536 Kind regards, -- Arx Cruz Software Engineer Red Hat EMEA <https://www.redhat.com> arxcruz(a)redhat.com @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 1

[release] Release countdown for week R-20, Nov 23 - Nov 27
by Herve Beraud 27 Nov '20

27 Nov '20

Greetings Everyone! Development Focus ----------------- The Wallaby-1 milestone is next week, on December 03! Project team plans for the Wallaby cycle should now be solidified. General Information ------------------- If you planned to change the release model for any of your deliverables this cycle, please remember to do so ASAP, before milestone-1. Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library which had changes but has not been otherwise released since the Victoria release. PTL's or release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well, by posting a -1. If we do not hear anything at all by the end of the week, we will assume things are OK to proceed. NB: If one of your libraries is still releasing 0.x versions, start thinking about when it will be appropriate to do a 1.0 version. The version number does signal the state, real or perceived, of the library, so we strongly encourage going to a full major version once things are in a good and usable state. Upcoming Deadlines & Dates -------------------------- Wallaby-1 milestone: December 03 Hervé Beraud (hberaud) and the Release Management Team -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0