- openstack-discuss - lists.openstack.org

[manila] no meeting this week
by Tom Barron 21 Nov '18

21 Nov '18

Just a reminder that there will be no manila community meeting this week. Next manila meeting will be Thursday, 29 November, at 1500 UTC in #openstack-meeting-alt on freenode. Agenda here [1] - Feel free to add ... -- Tom Barron (tbarron) [1] https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting

1 0

[openstack-dev] [neutron] [drivers] Cancelling weekly meeting on November 23rd
by Miguel Lavalle 21 Nov '18

21 Nov '18

Dear Neutron team, Due to the Thanksgiving Holiday in the USA, several members of the team will not be able to attend the weekly meeting. Let's cancel it and resume normally on the 30th of November Best regards Miguel __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[infra] [zuul] [placement] Minimizing size/time of test node
by Chris Dent 21 Nov '18

21 Nov '18

I have a work in progress to run a little job in placement that gathers very simple performance numbers on some queries. This is being done as a sort of sanity check. As with many such things it is a bit rough around the edges and I'd like to make it smoother in a variety of ways. The WIP is at https://review.openstack.org/#/c/602484/ One of the ways I'd like to change it is to not rely on devstack. I need only mysql, uwsgi, python and the current revision of placement on the node. The current job uses devstack-minimal as its base but that's overkill and slow. What is the correct base job to use which, as long as I put the files in the right place, will gather the logs I want? Thanks. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

4 5

[openstack-dev] [zun] Failed to create Container
by Rania Adouni 21 Nov '18

21 Nov '18

Hi , I am starting to use zun on openstack pike , and when I try to lunch container with cirros image , I get this reason : Docker internal error: 500 Server Error: Internal Server Error ("legacy plugin: Post http://192.168.1.10:23750/Plugin.Activate: dial tcp 192.168.1.10:23750: connect: connection refused"). you can find here the log on my compute node :https://pastebin.com/nZTiTZiV. some help with this will be great . Best Regards, Rania Adouni __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

3 7

Re: [openstack-dev] [horizon] Do we want new meeting time?
by Ivan Kolodyazhny 21 Nov '18

21 Nov '18

Hi all, Due to the low activity on our weekly meeting, I would like to raise this question again. Do we want a new meeting day and/or time? I'm available any day except Tuesday and Wednesday. I'm going to get some feedback before I create a new poll. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Thu, Apr 5, 2018 at 1:42 PM Ivan Kolodyazhny <e0ne(a)e0ne.info> wrote: > Hi team, > > It's a friendly reminder that we've got voting open [1] until next > meeting. If you would like to attend Horizon meetings, please, select > comfortable options for you. > > [1] https://doodle.com/poll/ei5gstt73d8v3a35 > > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Wed, Mar 21, 2018 at 6:40 PM, Ivan Kolodyazhny <e0ne(a)e0ne.info> wrote: > >> Hi team, >> >> As was discussed at PTG, usually we've got a very few participants on our >> weekly meetings. I hope, mostly it's because of not comfort meeting time >> for many of us. >> >> Let's try to re-schedule Horizon weekly meetings and get more attendees >> there. I've created a doodle for it [1]. Please, vote for the best time for >> you. >> >> >> [1] https://doodle.com/poll/ei5gstt73d8v3a35 >> >> Regards, >> Ivan Kolodyazhny, >> http://blog.e0ne.info/ >> > > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[openstack-dev] VM stalls with the console log "Exiting boot services and installing virtual address map"
by Srikanth Kumar Lingala 21 Nov '18

21 Nov '18

Hi, I am working with OpenStack stable/pike release in Ubuntu 18.04. When I am trying to spawn VM, which is worked in the earlier OpenStack releases, VM is stalled with the following log in the VM console logs: EFI stub: Booting Linux Kernel... EFI stub: Generating empty DTB EFI stub: Exiting boot services and installing virtual address map... I am observing that VM is in Running status, without any error logs. And, VM is booting with UEFI support. But, I am not able to get VM Console. Earlier I didn't observe this. How can I disable UEFI support, while spawning VM's in OpenStack Nova-Compute. My Libvirt version is 4.0.0. Can someone help me to fix the issue. Regards, Srikanth. -- ---- Srikanth. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[kayobe] Forum summary
by Mark Goddard 21 Nov '18

21 Nov '18

Hi, Thanks to those who attended the kayobe forum session. I'll try to summarise the key points here. The etherpad is here: https://etherpad.openstack.org/p/BER-18-kayobe-feedback-roadmap. - Several people were keen for a Rocky release. We're working on this currently, and aim to make it a small one so that we can move to Stein. - The point was raised that the locally installed environment can be hard to keep in sync, and the installation procedure is too complex. We hope to resolve this for the rocky release via https://storyboard.openstack.org/#!/story/2004252 and https://storyboard.openstack.org/#!/story/2004367. - Documentation is lacking in a few areas. We aim to improve this for rocky: https://storyboard.openstack.org/#!/story/2004360. - Ability to import configuration of an existing deployment from kolla-ansible: https://storyboard.openstack.org/#!/story/2004364 - Document/automate bifrost backup procedure: https://storyboard.openstack.org/#!/story/2004359 A few people also requested that we start a regular IRC meeting. Up to now we've favoured ad-hoc IRC communication, but I tend to agree that the time is right. I'll send out a separate email with a poll. Cheers, Mark

1 0

[Openstack] [OpenStack][Compute-Neutron] Is it possible to create flat network from different NICs
by Soheil Pourbafrani 21 Nov '18

21 Nov '18

Hi, I installed OpenStack on One node (for test) and creating a flat external network I could connect VMs to the provider network (internet). In the production environment, we have 4 NIC on each server and each server (compute node) will run 4 instances. My question is, is it possible to create a separate external network based on each NIC (so 4 external networks) and run each instance using one of them? _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

2 2

[heat] Meeting canceled this week
by Rico Lin 21 Nov '18

21 Nov '18

Hi team Since we just have summit last week, let's not over-occupied all member's time. we shall resume meeting next week -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[keystone][nova] Availability zones and unified limits
by Lance Bragstad 21 Nov '18

21 Nov '18

Unified limits cropped up in a few discussions last week. After describing the current implementation of limits, namely the attributes that make up a limit, someone asked if availability zones were on the roadmap. Ideally, it sounded like they had multiple AZs in a single region, and they wanted to be able to limit usage within the AZ. With the current implementation, regions would be the smallest unit of a deployment they could limit (e.g., limit project Foo to only using 64 compute cores within RegionOne). Instead, the idea would be to limit the number of resources for that project on an AZ within a region. What do people think about adding availability zones to limits? Should it be an official attribute in keystone? What other services would need this outside of nova? There were a few other interesting cases that popped up, but I figured we could start here. I can start another thread if needed and we can keep this specific to discussing limits + AZs. Thoughts?

4 5