- openstack-discuss - lists.openstack.org

[neutron] bug deputy report
by Takashi Yamamoto 26 Nov '18

26 Nov '18

Critical https://bugs.launchpad.net/neutron/+bug/1803745 neutron-dynamic-routing: unit test failures with master branch of neutron High https://bugs.launchpad.net/neutron/+bug/1804180 Neutron ovs cleanup cannot run on Windows https://bugs.launchpad.net/neutron/+bug/1794718 Neutron VPNAAS don't update site connections on python3 https://bugs.launchpad.net/neutron/+bug/1799737 l3 agent external_network_bridge broken with ovs Medium https://bugs.launchpad.net/neutron/+bug/1804327 occasional connection reset on SNATed after tcp retries Low https://bugs.launchpad.net/neutron/+bug/1803723 [fwaas] _is_supported_by_fw_l2_driver method is hard linked to the default ML2/OVS core plugin implementation https://bugs.launchpad.net/neutron/+bug/1804274 Neutron error agreggation interfaces https://bugs.launchpad.net/neutron/+bug/1804259 DB: sorting on elements which are AssociationProxy fails Undecided https://bugs.launchpad.net/neutron/+bug/1802971 tempest volume_boot_pattern and basic_ops running concurrently causing timeouts RFE https://bugs.launchpad.net/neutron/+bug/1804634 [RFE] l3_agent should separate router_info creation logic Incomplete https://bugs.launchpad.net/neutron/+bug/1803919 [L2] dataplane down during ovs-agent restart https://bugs.launchpad.net/neutron/+bug/1804842 When kill(sometines doesn't restart) the ovs switch or restart it in the compute nodes vm conectivity is lost https://bugs.launchpad.net/neutron/+bug/1804173 Metadata proxy server SSL handshake problem if Python >= 3 https://bugs.launchpad.net/neutron/+bug/1802736 Reporting to Jaeger with OSProfiler doesn't work https://bugs.launchpad.net/neutron/+bug/1801738 Assigning a FIP to NLBaaS VIP port doesn't affect Designate https://bugs.launchpad.net/neutron/+bug/1801779 Policy rule rule:create_port:fixed_ips:subnet_id doesn't allow non-admin to create port on specific subnet

1 0

[nova] [placement] placement functional testing
by Chris Dent 26 Nov '18

26 Nov '18

When https://review.openstack.org/#/c/617941/ merges (probably today), nova will be running its functional tests against openstack/placement and the existing unit and functional tests in nova that were solely testing placement will be gone. Tests like those in functional/test_servers.py will still be testing against real placement code, using a PlacementFixture that establishes a in-process placement service and an in-RAM database. If you have changes in progress that use placement anywhere in your functional tests it is quite likely you will have some merge conflicts. I tried to make it so that in most cases you don't need to do anything to have a working placement: If you're using the Intergated Helpers, it ought to just work. But if it doesn't please ask here, or find me in IRC and I can try to help. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 0

[openstack-dev] [glance] about use shared image with each other
by Rambo 26 Nov '18

26 Nov '18

Hi,all Recently, I want to use the shared image with each other.I find it isn't convenient that the producer notifies the consumer via email which the image has been shared and what its UUID is. In other words, why the image api v2 is no provision for producer-consumer communication? To make it is more convenient, if we can add a task to change the member_status from "pending" to "accepted" when we share the image with each other. It is similar to the resize_confirm in Nova, we can control the time interval in config. Can you tell me more about this?Thank you very much! Best Regards Rambo __________________________________________________________________________ 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

2 3

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage
by Bogdan Dobrelya 26 Nov '18

26 Nov '18

Here is a related bug [1] and implementation [1] for that. PTAL folks! [0] https://bugs.launchpad.net/tripleo/+bug/1804822 [1] https://review.openstack.org/#/q/topic:base-container-reduction > Let's also think of removing puppet-tripleo from the base container. > It really brings the world-in (and yum updates in CI!) each job and each > container! > So if we did so, we should then either install puppet-tripleo and co on > the host and bind-mount it for the docker-puppet deployment task steps > (bad idea IMO), OR use the magical --volumes-from <a-side-car-container> > option to mount volumes from some "puppet-config" sidecar container > inside each of the containers being launched by docker-puppet tooling. On Wed, Oct 31, 2018 at 11:16 AM Harald Jensås <hjensas at redhat.com> wrote: > We add this to all images: > > https://github.com/openstack/tripleo-common/blob/d35af75b0d8c4683a677660646… > > /bin/sh -c yum -y install iproute iscsi-initiator-utils lvm2 python > socat sudo which openstack-tripleo-common-container-base rsync cronie > crudini openstack-selinux ansible python-shade puppet-tripleo python2- > kubernetes && yum clean all && rm -rf /var/cache/yum 276 MB > > Is the additional 276 MB reasonable here? > openstack-selinux <- This package run relabling, does that kind of > touching the filesystem impact the size due to docker layers? > > Also: python2-kubernetes is a fairly large package (18007990) do we use > that in every image? I don't see any tripleo related repos importing > from that when searching on Hound? The original commit message[1] > adding it states it is for future convenience. > > On my undercloud we have 101 images, if we are downloading every 18 MB > per image thats almost 1.8 GB for a package we don't use? (I hope it's > not like this? With docker layers, we only download that 276 MB > transaction once? Or?) > > > [1] https://review.openstack.org/527927 -- Best regards, Bogdan Dobrelya, Irc #bogdando

1 0

[openstack-dev] [nova][placement] Please help to review XenServer vgpu related patches
by Naichuan Sun 26 Nov '18

26 Nov '18

Hi, Sylvain, Jay, Eric and Matt, I saw the n-rp and reshaper patches in upstream have almost finished. Could you help to review XenServer vGPU related patches when you have the time? https://review.openstack.org/#/c/520313/ https://review.openstack.org/#/c/521041/ https://review.openstack.org/#/c/521717/ Thank you very much. BR. Naichuan Sun __________________________________________________________________________ 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

[neutron] LP tag for python 3
by Takashi Yamamoto 26 Nov '18

26 Nov '18

hi, currently we seem to have an official tag "py34" on the LP. and "py35" is documented in the contributor guide. https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#py… i'd like to propose to replace them with "py3" mechanically.

2 1

[Openstack] [OpenStack][Cinder]How config cinder.conf [nova] part for InstanceLocalityFilter
by Soheil Pourbafrani 25 Nov '18

25 Nov '18

Hi, I want to enable InstanceLocalityFiletr for the Cinder. I set scheduler_default_filters = AvailabilityZoneFilter,CapacityFilter,CapabilitiesFilter,InstanceLocality But the document said we should specify an account with privileged rights for Nova in Cinder configuration (configure a keystone authentication plugin in the [nova] section), but I can't find an example for such configuration. Can anyone give an example? _______________________________________________ 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

1 0

[Openstack] [OpenStack][Cinder] Config Volumes to Store on Compute nodes
by Soheil Pourbafrani 25 Nov '18

25 Nov '18

Hi, I want to configure cinder to store Volumes on the Compute nodes. I know I should use the InstanceLocalityFilter. Suppose we have one Controller and two Compute node, should I install the Cinder on each node (Controller and Compute)? I will be appreciated if you suggest me any instruction about this. Thanks! _______________________________________________ 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

1 0

[Openstack] [openstack][neutron]Iptables snat not work when securitygroup is on
by 陈炤 25 Nov '18

25 Nov '18

Hi, I am building an openstack all-in-one environment in a CentOS7.4 machine. For some reason I have only one network interface(eth0) and one ip address, so I created a linux bridge(br0), and forwarded datas to eth0 using iptables command: iptables -t nat -A POSTROUTING -s {bridge virtual ip} -j SNAT --to {eth0 ip} But it seems not work. When I ping to 8.8.8.8 from br0 and run tcpdump, I can see that datas can be forwared to eth0 and be sent to 8.8.8.8, but when datas are sent back to eth0, they can not be forwarded to br0. Ip forwarding, net.bridge.bridge-nf-call-iptables and net.bridge.bridge-nf-call-ip6tablesare set to 1. If I close security group by setting securitygroup = false, this rule works fine, but if I use iptables -F instead, the rule is not work. Does the securitygroup have a magic to trap iptables? BR Don _______________________________________________ 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 1

[openstack-dev] [kolla] Berlin summit resume
by Eduardo Gonzalez 24 Nov '18

24 Nov '18

Hi kollagues, During the Berlin Summit kolla team had a few talks and forum discussions, as well as other cross-project related topics [0] First session was ``Kolla project onboarding``, the room was full of people interested in contribute to kolla, many of them already using kolla in production environments whiling to make upstream some work they've done downstream. I can say this talk was a total success and we hope to see many new faces during this release putting features and bug fixes into kolla. Slides of the session at [1] Second session was ``Kolla project update``, was a brief resume of what work has been done during rocky release and some items will be implemented in the future. Number of attendees to this session was massive, no more people could enter the room. Slides at [2] Then forum sessions.. First one was ``Kolla user feedback``, many users came over the room. We've notice a big increase in production deployments and some PoC migrating to production soon, many of those environments are huge. Overall the impressions was that kolla is great and don't have any big issue or requirement, ``it works great`` became a common phrase to listen. Here's a resume of the user feedback needs [3] - Improve operational usage for add, remove, change and stop/start nodes and services. - Database backup and recovery - Lack of documentation is the bigger request, users need to read the code to know how to configure other than core/default services - Multi cells_v2 - New services request, cyborg, masakari and tricircle were the most requested - SElinux enabled - More SDN services such as Contrail and calico - Possibility to include user's ansible tasks during deploy as well as support custom config.json - HTTPS for internal networks Second one was about ``kolla for the edge``, we've meet with Edge computing group and others interested in edge deployments to identify what's missing in kolla and where we can help. Things we've identified are: - Kolla seems good at how the service split can be done, tweaking inventory file and config values can deploy independent environments easily. - Missing keystone federation - Glance cache support is not a hard requirement but improves efficiency (already merged) - Multi cells v2 - Multi storage per edge/far-edge - A documentation or architecture reference would be nice to have. Last one was ``kolla for NFV``, few people came over to discuss about NUMA, GPU, SRIOV. Nothing noticiable from this session, mainly was support DPDK for CentOS/RHEL,OracleLinux and few service addition covered by previous discussions. [0] https://etherpad.openstack.org/p/kolla-stein-summit [1] https://es.slideshare.net/EduardoGonzalezGutie/kolla-project-onboarding-ope… [2] https://es.slideshare.net/EduardoGonzalezGutie/openstack-kolla-project-upda… [3] https://etherpad.openstack.org/p/berlin-2018-kolla-user-feedback [4] https://etherpad.openstack.org/p/berlin-2018-kolla-edge [5] https://etherpad.openstack.org/p/berlin-2018-kolla-nfv __________________________________________________________________________ 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 2