Re: [Openstack] Instances do not have access to internet

On Sep 28, 2016, at 5:32 PM, Imran Khakoo wrote: > I did add this rule to default security group, that was the first thing > before I even launched an instance. Yeah, that should have done it. > Egress IPv4 Any Any 0.0.0.0/0 - > Egress IPv4 ICMP Any - default > Egress

Re: [Openstack] Instances do not have access to internet

On Sep 28, 2016, at 4:07 PM, Imran Khakoo wrote: > I can ping instances and SSH into them just fine, but I can't seem to get > internet access on the instances. Maybe a security group is blocking it? To do a trace from an instance to the 'Net, you'd need to open up for ICMP traffic. But I'd

[Openstack] Multiple availability zones

Thanx everyone in helping me figure out how I wanted my multiple controller nodes setup - using keepalived and load balance the services with that is well under way and so far it looks like it's working. I still have to fine-tune and finish that work of. But modifying my setup scripts etc to set

[Openstack] Provisioning VMs in Openstack cluster

Hi All, We are trying to provision a few VM images in a small Openstack cluster. Our image is about 3GB size. It has taken six minutes to provision just three VMs, one on each host; and it grows linearly. Now, we are wondering it may take 200 minutes for 100 VMs to be ready. That would be

Re: [Openstack] Provisioning VMs in Openstack cluster

On Sep 28, 2016, at 8:34 PM, Leon Liu wrote: > We are trying to provision a few VM images in a small Openstack cluster. Our > image is about 3GB size. It has taken six minutes to provision just three > VMs, one on each host; and it grows linearly. Now, we are wondering it may > take 200 minutes

Re: [Openstack] Provisioning VMs in Openstack cluster

But what I _think_ I've seen (can't be absolutly sure, because I never investigated in detail) is that Cinder seems to be 'idling' a little to much. It starts creating the volume, then waits for a while, then starts sending the image to the volume, then waits and waits, and then the process

Re: [Openstack] Provisioning VMs in Openstack cluster

OK, thanks. I better check that more -Original Message- From: Turbo Fredriksson [mailto:tu...@bayour.com] Sent: Wednesday, September 28, 2016 4:04 PM To: Leon Liu Cc: openstack@lists.openstack.org Subject: Re: [Openstack] Provisioning VMs in Openstack cluster But what I _think_

Re: [Openstack] Instances do not have access to internet

Hi, I did add this rule to default security group, that was the first thing before I even launched an instance. I'm still a newbie so I may be missing something? Direction Ether Type IP Protocol Port Range Remote IP Prefix Remote Security Group Actions Egress IPv4 Any Any 0.0.0.0/0 - Delete Rule

[Openstack] Instances do not have access to internet

Hello, I performed an Autopilot/Landscape install. I can ping instances and SSH into them just fine, but I can't seem to get internet access on the instances. I can even ping from one instance to the other. I can also ping the Openstack router from the instances. If I juju ssh into the nova and

[Openstack] Nova-Glance Query

Hi, I am using python-openstackclient and os_client_config My requirement is, i want to update, my image metadata i made two objects, by which i think i may achieve it: nova = os_client_config.make_client('compute') glance = os_client_config.make_client('images') example: metadata =

Re: [Openstack] Nova-Glance Query

Amit, For Glance, all the user-specified image metadata must be String data type. You can see this in the image schema [0], where "additionalProperties": {"type": "string"} (The only image properties that are *not* strings are those assigned non-string types in the schema.) So for your

Re: [openstack-dev] [puppet] Proposing David Moreau Simard part of Puppet OpenStack CI core team

On 09/28/2016 10:06 AM, Emilien Macchi wrote: Until now, we had no specific team for dealing with Puppet OpenStack CI (aka openstack/puppet-openstack-integration project). But we have noticed that David was doing consistent work to contribute to Puppet OpenStack CI by adding more coverage, but

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Here you go Flavio, Sergey and team collected some information from fuel-ccp efforts. Design for OpenStack Containerized Control Plane : https://review.openstack.org/#/c/378266/ Design document for clustering services on k8s : https://review.openstack.org/#/c/378244/ Add test plan/results for

[openstack-dev] TC Candidacy

Hello! I am announcing my candidacy for a position on the OpenStack Technical Committee. For those who do not know me, I have been involved with OpenStack since the very beginning, working for Rackspace as a core member of the Nova team. An internal job change took me away from active development

Re: [openstack-dev] [puppet] Proposing David Moreau Simard part of Puppet OpenStack CI core team

+1 from me, David is doing an awesome job in p-o-i =) 2016-09-28 13:08 GMT-03:00 Rich Megginson : > On 09/28/2016 10:06 AM, Emilien Macchi wrote: > >> Until now, we had no specific team for dealing with Puppet OpenStack >> CI (aka openstack/puppet-openstack-integration

[openstack-dev] [Ironic] The Ironic Grenade gate job is currently broken. Please don't do recheck on patches

Currently the Ironic Grenade gate job is broken. Until the issue is resolved please don't do recheck on openstack/ironic patch. Work is ongoing to figure out why it stopped working. __ OpenStack Development Mailing List

Re: [openstack-dev] [neutron][lbaas][heat][octavia] Heat engine doesn't detect lbaas listener failures

But in the lbaas db, all lbaas resources have the provisioning_status and operating_status fields[1]. [1] http://git.openstack.org/cgit/openstack/neutron-lbaas/tree/neutron_lbaas/db/loadbalancer/models.py#n352 Also there are apis which allows drivers to maintain them[2]. [2]

[openstack-dev] TC candidacy

Despite its name, the Technical Committee has become the part of the OpenStack contributor community that enshrines, defines, and -- in some rare cases -- enforces what it means to be "OpenStack". Meanwhile, the community has seen a great deal of growth and change. Some of these changes have

Re: [Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

Yeah, I saw that in his response. Sounds like a good option if you want to try it. I hadn’t tried it only because I didn’t know about it at the time, and the older version was working fine for us on our other hosts. Mike Smith Lead Cloud Systems Architect Overstock.com

Re: [openstack-dev] [horizon] Integration Tests Status

Integration tests are now non-voting, so feel free to recheck failing builds. Rob On 28 September 2016 at 14:23, Rob Cresswell > wrote: Hi all, So the integration tests have started failing all over the place again. Given the

[openstack-dev] [tripleo] Getting the UI to talk with Undercloud API service endpoints

Hi - I want to bring up a subject that needs a little more attention. There are a few ideas floating around but it's important that we get this done right. UI is unique in the sense that it operates almost entirely in a browser, talking directly to service API endpoints which it either figures

[openstack-dev] [tricircle]tricircle cleaning plan

Hello, The Newton branch will be created tomorrow, we can start the Tricircle cleaning in the trunk to make Tricircle dedicated for networking automation. At the same time Tricircle Newton release will be done in the Newton branch, two more patches needed for this branch: one patch to update

Re: [openstack-dev] [Solum] Nominating Zhu Rong for Solum core

+1 From: Devdatta Kulkarni Date: Wed, Sep 28, 2016 at 8:32 AM Subject: [Solum] Nominating Zhu Rong for Solum core To: openstack-dev@lists.openstack.org Hi team, I would like to propose Zhu Rong (irc: zhurong) to be included as Solum core. Zhu Rong has been very

Re: [openstack-dev] [all][elections][TC] TC Candidacy

I noticed a good statement, marked it inline. On 9/28/16 7:24 AM, John Davidge wrote: > Hi Zane, > > Thanks for pointing this out! My interpretation of the StackForge > Retirement page[1] was wrong on that point. I've updated the blog post to > reflect that (without removing the original

Re: [openstack-dev] [Solum] Nominating Zhu Rong for Solum core

+1 Look forward to more contributions from you! On Wed, Sep 28, 2016 at 8:32 AM, Devdatta Kulkarni < kulkarni.devda...@gmail.com> wrote: > Hi team, > > I would like to propose Zhu Rong (irc: zhurong) to be included as Solum > core. > > Zhu Rong has been very active in different parts of Solum

[openstack-dev] [puppet] Proposing David Moreau Simard part of Puppet OpenStack CI core team

Until now, we had no specific team for dealing with Puppet OpenStack CI (aka openstack/puppet-openstack-integration project). But we have noticed that David was doing consistent work to contribute to Puppet OpenStack CI by adding more coverage, but also helping when things are broken. David is

[openstack-dev] [release][glance] glance Newton RC2 available

Hello everyone, A new release candidate for glance for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/glance/glance-13.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-announce] [new][watcher] watcher-dashboard 0.5.0 release (newton)

We are tickled pink to announce the release of: watcher-dashboard 0.5.0: Watcher Management Dashboard This release is part of the newton release series. For more details, please see below. Changes in watcher-dashboard 0.4.0..0.5.0 - 9b48df4 Added action

Re: [openstack-dev] TC candidacy

On 28/09/2016 12:41 PM, Chris Dent wrote: > > * Information is not always clear nor clearly available, despite > valiant efforts to maintain a transparent environment for the > discussion of policy and process. There is more that can be done > to improve engagement and communication. Maybe

[openstack-dev] [release][freezer] freezer Newton RC2 available

Hello everyone, A new release candidate for freezer for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer/freezer-3.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a release candidate respin, these

[Openstack-operators] [ansible] Best practice for single interface cconfig

It's been a while since I deployed OpenStack from scratch so I'm using the Ansible install guide [1] and ran into a problem: How should the hosts be configured for hosts that have one NIC? The test environment layout with one interface [2] is what I'm following but the /etc/network/interface

Re: [openstack-dev] Devstack, Tempest, and TLS

On Tue, Sep 27, 2016, at 02:58 PM, Clark Boylan wrote: > Once multinode testing has tls-proxy enabled the next thing I think we > should be talking about is enabling this by default in devstack. As > mentioned before ironic doesn't work due to IPA images not trusting > glance's cert. Swift's

Re: [openstack-dev] TC candidacy

On Wed, 28 Sep 2016, Jim Rollenhagen wrote: +1 to release notes or something of that like. i was asked to give an update on the TC internally and it seems the only information out there is to read through backlog of meeting logs or track the items that do get raised to ML. even then, it's hard

Re: [openstack-dev] TC candidacy

> On Sep 28, 2016, at 1:59 PM, Chris Dent wrote: > > On Wed, 28 Sep 2016, Jim Rollenhagen wrote: > +1 to release notes or something of that like. i was asked to give an update on the TC internally and it seems the only information out there is to read

Re: [openstack-dev] TC candidacy

On 28/09/2016 4:27 PM, Jeremy Stanley wrote: > As was pointed out elsewhere in the thread, the TC has been trying > to do something along these lines at > http://www.openstack.org/blog/category/technical-committee-updates/ > but even with a dedicated communication subteam (see the May 13, > 2015

Re: [openstack-dev] TC candidacy

On 28/09/2016 3:59 PM, Chris Dent wrote: > On Wed, 28 Sep 2016, Jim Rollenhagen wrote: > >> And the git tree, with a changelog, is here: >> http://git.openstack.org/cgit/openstack/governance/ > > I assume, but I'd prefer if he confirm, that the point gordc was > trying to make was that there's

[openstack-announce] [new][magnum] magnum-ui 2.1.1 release (newton)

We are mirthful to announce the release of: magnum-ui 2.1.1: Magnum User Interface This release is part of the newton stable release series. With source available at: http://git.openstack.org/cgit/openstack/magnum-ui Please report issues through launchpad:

Re: [openstack-dev] TC candidacy

On Wed, Sep 28, 2016 at 2:49 PM, gordon chung wrote: > > > On 28/09/2016 12:41 PM, Chris Dent wrote: > > > > * Information is not always clear nor clearly available, despite > > valiant efforts to maintain a transparent environment for the > > discussion of policy and process.

Re: [openstack-dev] TC candidacy

On 2016-09-28 20:59:09 +0100 (+0100), Chris Dent wrote: > Part of the point I was trying to make in the message to which gordc was > responding is that whereas a git tree can allow someone to dig through > and acquire details, a thing that is more like release notes[1] is far > more human oriented

[openstack-dev] [ironic] Petitboot and PXE

Hey ironic-ers, My team has a patch [1] up for enabling PXE for petitboot [2]. It's been around for awhile, and we actually use it in our PowerKVM CI ironic job (as our OpenPOWER target boxes run petitboot). I was hoping to get some eyes on it as we'd like to eventually get it upstream. I've

[openstack-dev] [horizon][keystone] retiring python-keystoneclient-kerberos

Hi there, I would like to retire the python-keystoneclient-kerberos repo [1]. The repo was pretty basic, it had a single auth plugin. The logic has since been copied over to keystoneauth1 and provided you have kerberos libraries installed the plugin will be available to you. The last release of

[openstack-dev] [release][murano] murano Newton RC2 available

Hello everyone, A new release candidate for murano for the end of the Newton cycle is available! You can find the source code tarballs at: https://tarballs.openstack.org/murano/murano-3.0.0.0rc2.tar.gz https://tarballs.openstack.org/murano-agent/murano-agent-3.0.0.0rc2.tar.gz

Re: [openstack-dev] TC candidacy

>> +1 to release notes or something of that like. i was asked to give an >> update on the TC internally and it seems the only information out there >> is to read through backlog of meeting logs or track the items that do >> get raised to ML. even then, it's hard to define what deliverables were >>

Re: [openstack-dev] [magnum] Fedora Atomic image that supports kubernetes external load balancer (for stable/mitaka)

Fantastic! Quick semi-related question. Will Magnum Newton be using lbaasv2? That is what we have implemented in Kolla. Regards -steve From: Ton Ngo Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday,

Re: [openstack-dev] [Security] XML Attacks and DefusedXML on Global Requirements

A completely secure alternative isn't available in the Python standard library. Here's a table of various XML libraries and the vulnerabilities they may be affected by [1]. This is partially reflected in Python's official documentation as well (version 2.7.12) [2]. There are currently 132

[openstack-dev] TC candidacy

I'd like to throw in my hat to serve the community as a TC member. My name is Jim Rollenhagen, but I'm better known in the community as jroll. I've worked in many environments, from 20-person startup to massive corporations. For the past three years, I've been working on OpenStack at Rackspace. I

Re: [Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

yes thx Corbin, I should try setting mem_stats_period_seconds = 0 in libvirt section of nova.conf and then restart nova-compute on all hosts. Then I can try the live-migration again and see if that prevents VMs from unexpected shutdowns. Hopefully this works, and maybe this goes away with 7.3

[openstack-dev] [release][Cinder] Cinder Newton RC2 available

Hello everyone, A new release candidate for Cinder for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cinder/cinder-9.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this

Re: [openstack-dev] [magnum] Fedora Atomic image that supports kubernetes external load balancer (for stable/mitaka)

Steve, In Newton, we upgraded the Heat templates to use lbaasv2 [1]. However, it seems the k8s external load balancer still work with lbaasv1. If Kolla doesn't use the external load balancer feature, it should be fine. [1] https://review.openstack.org/#/c/314060/ Best regards, Hongbin On Wed,

Re: [openstack-dev] [Keystone] Project name DB length

We may have to ask Adam or Dolph, or pull out the history textbook for this one. I imagine that trying to not bloat the token was definitely a concern. IIRC User name was 64 also, but we had to increase to 255 because we're not in control of name that comes from external sources (like LDAP). On

[openstack-dev] Deprecation Policies (related to Heka)

First off, apologies for missing most of the team meeting today. I have read through the logs and saw a discussion about deprecating heka. We need to ensure that we follow the deprecation policy. My understanding of the deprecation policy is as follows (in a nutshell): 1. We must

[openstack-dev] [infra]please help to add initial members to trio2o-core and trio2o-release group

Hello, Trio2o is a new project which is derived from Tricircle: https://review.openstack.org/#/c/367114/ Please add the initial members (same as that in Tricircle) to the group trio2o-core (https://review.openstack.org/#/admin/groups/1576,members) and trio2o-release

[openstack-dev] SRIOV-port refused to bind

Hi I am using the SRIOV on mitaka. When I try to launch the VM with SRIOV port its failed. When I see the neutrn-server.log I see that below message on controller. ddf81 - - -] Refusing to bind due to unsupported vnic_type: direct bind_port

[openstack-dev] [trio2o]Trio2o cleaning discussion

Hello, As we discussed yesterday, we'll have a short conversation on the Trio2o cleaning. Let's discuss Trio2o cleaning on Friday UTC2:00(i.e, beijing time 10:00), 1 hour It would be better to discuss this in the channel of #openstack-trio2o instead of #openstack-tricircle(sorry mentioned

[openstack-dev] [Keystone] Project name DB length

Hello Keystone Devs, Just curious as to the choice to have the project name be only 64 characters: https://github.com/openstack/keystone/blob/master/keystone/resource/backends/sql.py#L241 Seems short, and an odd choice when the user.name field is 255 characters:

Re: [openstack-dev] [Keystone] Project name DB length

I think with PKI tokens we had worse to worry about! At any rate, would be great to know, and if there isn't a strong reason against it we can make project name 255 for some more flexibility. Plus although there is no true official standard, most projects in OpenStack seem to use 255 as the

[openstack-dev] [Neutron] Driver meeting cancelled for Thur Sept 29

__ 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-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

It unfortunately is affecting virtually all of Redhat's latest qemu-kvm packages. The bug that was unintentionally introduced was done so in response to CVE-2016-5403 Qemu: virtio: unbounded memory allocation on host via guest leading to DoS. Late in the bug thread, they finally posted to a new

Re: [openstack-dev] [nova] ops meetup feedback

Matt Riedemann wrote: On 9/28/2016 12:10 AM, Joshua Harlow wrote: ACTION: we should make sure workarounds are advertised better ACTION: we should have some document about "when cells"? This is a difficult question to answer because "it depends." It's akin to asking "how many

Re: [Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

Oh you can read it in the bug thread, but I forgot to mention, if you put in your nova.conf under the libvirt section mem_stats_period_seconds = 0, and restart nova on the destination (although i'd say just do it on both) it will no longer hit the bug. I tested this a couple weeks back with

Re: [openstack-dev] [magnum] Fedora Atomic image that supports kubernetes external load balancer (for stable/mitaka)

Thanks Steve. We indeed have been using the image built by Yolanda's DIB elements and things have been stable. Dane and I have resolved the problems with the load balancer at least for the LBaaS v1. For LBaaS v2, we need to build a new image with Kubernetes 1.3 and we just got one built today.

[OpenStack-Infra] Connectivity issues in the gate

Hi all, I believe since yesterday we started seeing really bad external connectivity issues in Heat function tests. http://logs.openstack.org/52/359852/4/gate/gate-heat-dsvm-functional-convg-mysql-lbaasv2/7f45043/console.html is one of the numerous example. We try to fetch a fedora image from

Re: [openstack-dev] [octavia] Multi-node controller testing

Refloating this thread. I posted this rfe/bug [1], and I'm planning to come up with an experimental job that triggers one of the basic neutron/lbaas tests with octavia. I wonder if even picking up the scenario one for now could make sense, it's not very stable at the moment, but may be spreading

Re: [openstack-dev] os-loganalyze, project log parsing, or ...

On Wed, Sep 28, 2016, at 07:15 AM, Sean Dague wrote: > On 09/27/2016 06:19 PM, Andrew Laski wrote: > > > > > I totally understand where you're coming from. I just see it > > differently. > > > > The way it was done did not affect any other projects, and the plumbing > > used is something that

Re: [openstack-dev] os-loganalyze, project log parsing, or ...

On 09/27/2016 06:19 PM, Andrew Laski wrote: > > I totally understand where you're coming from. I just see it > differently. > > The way it was done did not affect any other projects, and the plumbing > used is something that could have easily be left in. And as luck would > have it there's

Re: [Openstack-operators] L3 HA Router

I figured this might be the case, but can you tell how I can locate the interface for the router namespace, if I do a ifconfig –a on the network node, I only see the br-* interfaces and the physical ones. I assume, I’d need to take down one of the interfaces that keepalived is responsible for,

Re: [Openstack-operators] L3 HA Router

Hello, Some work was done in that area however it was never completed. https://bugs.launchpad.net/neutron/+bug/1370033 You can issue an ugly failover by taking down the "ha" interface in the router namespace of the master with ifconfig down. But it's not pretty. Best regards On 09/28/2016

Re: [openstack-dev] [all][elections][TC] TC Candidacy

Hi Zane, Thanks for pointing this out! My interpretation of the StackForge Retirement page[1] was wrong on that point. I've updated the blog post to reflect that (without removing the original interpretation). The discussion about renaming git repos is a bit of a red herring, because what we're

Re: [openstack-dev] [tricircle]freeze date and patches to be merged for Newton release

Thank you all for the great effort, now only two patches of MUST TO HAVE are on the way to be merged: https://review.openstack.org/#/c/372414/ installation update https://review.openstack.org/#/c/326192/ volume detach Best Regards Chaoyi Huang (joehuang) From:

Re: [openstack-dev] [nova] [devstack] nova-api did not start

Hi Tony, As you suggest, I find the reason of this problem. I have removed "API_WORKES=0" in local.conf. It works. Thanks very much. Best Regards, xiangxinyong Tony Breeds 于2016年9月28日周三 上午11:28写道： > On Wed, Sep 28, 2016 at 11:10:52AM +0800, xiangxinyong wrote: > > Hi

[openstack-dev] [release][horizon] horizon Newton RC2 available

Hello everyone, A new release candidate for horizon for the end of the Newton cycle was generated, to catch release-critical fixes and include recent translations. You can find the source code tarball at: [...] Unless new release-critical issues are found that warrant a release candidate

[openstack-dev] Adding new functionality to networking scenario tests in tempest

Hi, I'm working on adding new tests to the networking scenario tests. I see that there is a class named "NetworkScenarioTest" in manager.py file. In that class, there are some helpers functions like '_create_network', 'create_subnet', ... Is this the place to add more helpers functions like

[openstack-dev] [vitrage] Barcelona design sessions

Hi, There will be three Vitrage design sessions in Barcelona: Wednesday 15:05-15:45: workroom Wednesday 15:55-16:35: fishbowl Wednesday 17:55-18:35: workroom I gathered the ideas that were raised in the etherpad below, and created a draft for the design session discussions. I’ll be happy to

Re: [openstack-dev] os-loganalyze, project log parsing, or ...

Excerpts from Andrew Laski's message of 2016-09-27 11:36:07 -0400: > Hello all, > > Recently I noticed that people would look at logs from a Zuul née > Jenkins CI run and comment something like "there seem to be more > warnings in here than usual." And so I thought it might be nice to > quantify

Re: [openstack-dev] [ironic] Next API meeting cancelled

On Thu, Sep 22, 2016 at 2:30 PM, Devananda van der Veen wrote: > Considering I'm the only one currently working on it / bringing up new > topics, I > think biweekly is a better match to the pace I'm working on this. > > However, I hope that changes after the summit /

[openstack-dev] [Solum] Nominating Zhu Rong for Solum core

Hi team, I would like to propose Zhu Rong (irc: zhurong) to be included as Solum core. Zhu Rong has been very active in different parts of Solum over several months now. His primary contribution has been moving Solum to use Oslo libraries, thereby making our project satisfy one of the

Re: [Openstack-operators] L3 HA Router

Hello, Please note that this is not recommended but it's currently the least invasive way (i.e not killing the machine or the keepalived process). * Get the UUID of the L3 router. * Go to the node that hosts your L3 routers (running the neutron-l3-agent service) and show all interfaces in that

Re: [openstack-dev] [octavia] Multi-node controller testing

I just found this one created recently, and I will try to build on top of it: https://review.openstack.org/#/c/371807/12 On Wed, Sep 28, 2016 at 1:52 PM, Miguel Angel Ajo Pelayo wrote: > Refloating this thread. > > I posted this rfe/bug [1], and I'm planning to come up

[openstack-dev] [networking-cisco] networking-cisco IRC meetings

TL;DR networking-cisco IRC meetings will be held bi-weekly on #openstack-meeting-3 starting from 2016/10/11 With the results of the doodle poll, and some pointers from Steve and Jeremy (thanks guys for the info) I've successfully organised the time and place for the networking-cisco IRC

[openstack-dev] [horizon] Integration Tests Status

Hi all, So the integration tests have started failing all over the place again. Given the number of failures over the past few weeks I've put up a patch to make them non-voting [1]. Please stop rechecking patches until this merges. Reviewers, please be sure to check the test logs when they

[Openstack-operators] L3 HA Router

OS: Ubuntu 14.04 OpenStack Liberty Is it possible to perform a manual failover of HA routers between master and backup by any sensible means ? ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org

[openstack-dev] [tricircle]agenda of weekly meeting Sept.28

Agenda of Sept.28 weekly meeting, let's continue the topics: # Newton cycle design summit planning: https://etherpad.openstack.org/p/ocata-tricircle-sessions-planning # patch review before freeze date Sept.30 # open discussion How to join: # IRC meeting:

[openstack-dev] [ironic] Newton post-mortem

Similar to keystone/neutron/nova, I thought it would be healthy for us to do a post-mortem on the Newton cycle. Here's the etherpad: https://etherpad.openstack.org/p/ironic-newton-retrospective Let's try to keep it troll-free (I know it's hard). Also note I put a poll about having a summit

[Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

Hi, I have problems with nova live-migration for my CentOS7 and RHEL7 VMs. The live migrations works fine for Windows2012R2 and Ubuntu1404 VMs. For CentOS7/RHEL based images I get this error in the Destination node in nova-compute.log. Also console for logged in VM users on the VM freeze.

Re: [Openstack-operators] L3 HA Router

Thank you, this was very helpful From: Tobias Urdin Date: Wednesday 28 September 2016 at 12:43 To: David Orn Johannsson Cc: "openstack-operators@lists.openstack.org" Subject: Re: [Openstack-operators] L3 HA Router Hello, Please note that this is

Re: [Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

There is a bug in the following: qemu-kvm-1.5.3-105.el7_2.7 qemu-img-1.5.3-105.el7_2.7 qemu-kvm-common-1.5.3-105.el7_2.7 Are you running these versions? We encountered this same issue and fixed it by running "yum downgrade qemu-kvm qemu-kvm-common qemu-img” which took us back to the el7_2.4

Re: [Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

What's your qemu version, and what does the libvirt log on the destination say? You may have hit this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1371943 There are some workarounds listed there, and downgrading also fixes it. Marcus. On 29 Sep 2016 00:35, "William Josefsson"

Re: [openstack-dev] [nova] ops meetup feedback

On 9/28/2016 12:10 AM, Joshua Harlow wrote: ACTION: we should make sure workarounds are advertised better ACTION: we should have some document about "when cells"? This is a difficult question to answer because "it depends." It's akin to asking "how many nova-api/nova-conductor processes should

[openstack-dev] [sahara] Skip next meeting

Hi team, Since all of us are preparing for future summit and there is no specific topics to cover, I think that we should skip meeting tomorrow at Sept 29. If there is topic to discuss, please write email to mailing list about your topic. PS: Please, continue sharing your ideas about future

Re: [Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

thanks Mike! yes, I checked and I've got the versions you mentioned installed: yum list installed | grep "qemu-" qemu-img.x86_64 10:1.5.3-105.el7_2.7 @updates qemu-kvm.x86_64 10:1.5.3-105.el7_2.7 @updates qemu-kvm-common.x86_64 10:1.5.3-105.el7_2.7

Re: [Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

> There is a bug in the following: > > qemu-kvm-1.5.3-105.el7_2.7 > qemu-img-1.5.3-105.el7_2.7 > qemu-kvm-common-1.5.3-105.el7_2.7 You might be better of using the RHEV qemu packages They are more recent (2.3) and have more features compiled into them. Cheers, Robert van Leeuwen

Re: [Openstack-operators] Nova live-migration failing for RHEL7/CentOS7 VMs

William - That is probably what you have hit then. There are several bug tickets out there that are related, I don’t have the specific one I found handy but it’s similar to the one Marcus just posted. I found it by Googling around for the error late one night. In our case, we had most of

[Openstack-operators] : Public cloud operators group in

I've followed "cloud for at least as long as OpenStack has existed, but back then I followed whatever/whoever called themselves "cloud" or "cloud-{app|service|etc}" and at one point there was a heated discussion (mostly that the rest of the group agreed with) that you couldn't claim you ran in