Re: [Openstack] How to connect host network with each tenant network?

2017-06-15 7:01 GMT+00:00 duhongwei : > > Hi guys, > > Now I'm using a vlan based Neutron network and there's no IP overlap. > Meanwhile I want to let the physical hosts be able to access each of the > tenant vlan networks (still keep tenant networks isolated). > > Any ideas?

Re: [Openstack] [gerrit] Co-authorship/ownership

2017-04-25 13:34 GMT+00:00 Eric Fried : > Howdy folks. > > What's the protocol when a change set has more than one (significant) > contributor? I've seen this "Co-Authored-By" tag in commit messages - > under what circumstances is it necessary/appropriate to use that? What >

Re: [OpenStack-Infra] Problem with OpenStack bot? Vitrage meeting was not recorded

2017-04-19 10:56 GMT+00:00 Afek, Ifat (Nokia - IL/Kfar Sava) : > Well, someone tried to say “Hi” in Chinese – could it be that? ☺ > I also see that some of my characters turned our wrong. Don’t know why. > Anyway, if the text file is there (I didn’t notice it), then I guess

Re: [Openstack] Nova connects to rabbitmq on localhost during migrate (ocata)

Sorry for forgetting to CC the ML on my first reply. 2017-04-06 13:19 GMT+00:00 Kim Gert Nielsen <k...@one.com>: > On Thu, Apr 06, 2017 at 12:49:23PM +0000, Jens Rosenboom wrote: >> 2017-04-06 11:37 GMT+00:00 Kim Gert Nielsen <k...@one.com>: >> > Hi, >&

Re: [openstack-dev] How to find "ovs_mechanism + vxlan tanent_type_driver + L2_pop" configure steps?

2017-03-31 3:10 GMT+00:00 Sam : > Hi all, > > In openstack-ocata install docs, I only found "linux_bridge + vxlan + l2pop" > configure steps, Is there "ovs+vxlan+l2pop" configure steps? The install-guide only covers the most basic setup, for ovs you will need to look at the

Re: [openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open

2017-03-31 2:00 GMT+02:00 Kendall Nelson : > > Hello All! > > Candidate proposals for the Technical Committee positions (7 positions) are > now open and will remain open until 2017-04-20, 23:45 UTC The table below states a much earlier closing time. > All candidacies must

Re: [openstack-dev] [neutron][nova] Config drive claims ipv6_dhcp, neutron api says slaac

2017-03-24 17:17 GMT+00:00 Clark Boylan <cboy...@sapwetik.org>: > On Fri, Mar 24, 2017, at 05:24 AM, Jens Rosenboom wrote: >> 2017-03-24 9:48 GMT+00:00 Jens Rosenboom <j.rosenb...@x-ion.de>: >> > 2017-03-24 9:30 GMT+00:00 Simon Leinen <simon.lei...@swit

Re: [openstack-dev] [neutron][nova] Config drive claims ipv6_dhcp, neutron api says slaac

2017-03-24 9:48 GMT+00:00 Jens Rosenboom <j.rosenb...@x-ion.de>: > 2017-03-24 9:30 GMT+00:00 Simon Leinen <simon.lei...@switch.ch>: >> Clark Boylan writes: >> [...] >>> { >>> "id": "network1", >>>

Re: [openstack-dev] [neutron][nova] Config drive claims ipv6_dhcp, neutron api says slaac

2017-03-24 9:30 GMT+00:00 Simon Leinen : > Clark Boylan writes: > [...] >> { >> "id": "network1", >> "link": "tap14b906ba-8c", >> "network_id": "7ee08c00-7323-4f18-94bb-67e081520e70", >> "type": "ipv6_dhcp" >>

Re: [Openstack] Deleting instance in error state does not free resources

2017-03-08 17:57 GMT+01:00 Georgios Dimitrakakis : > Hi all! > > I am setting up an Ocata installation from scratch and my problem is when > some instances come up in ERROR state (for various reasons). > > Since they are not usable when they are deleted they still continue to

Re: [openstack-dev] [infra][Neutron] Running out of memory on gate for linux bridge job

2017-01-13 17:56 GMT+01:00 Clark Boylan : > On Fri, Jan 13, 2017, at 07:48 AM, Jakub Libosvar wrote: >> Does anybody know whether we can bump memory on nodes in the gate >> without losing resources for running other jobs? >> Has anybody experience with memory consumption

Re: [openstack-dev] [nova] nova-api-metadata managing firewall

2017-01-10 4:33 GMT+01:00 Sam Morrison : > Hi nova-devs, > > I raised a bug about nova-api-metadata messing with iptables on a host > > https://bugs.launchpad.net/nova/+bug/1648643 > > It got closed as won’t fix but I think it could do with a little more > discussion. > >

Re: [openstack-dev] [devstack][neutron-lbaas][octavia] About installing Devstack on Ubuntu

2016-12-06 7:16 GMT+01:00 Yipei Niu : > Hi, All, > > I failed installing devstack on Ubuntu. The detailed info of local.conf and > error is pasted in http://paste.openstack.org/show/591493/. > > BTW, python2.7 is installed in Ubuntu, and Python.h can be found under >

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

2016-11-24 15:08 GMT+01:00 Lenny Verkhovsky : > Hi, > > The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI What OS is the CI running on? Can you show the output of "dnsmasq --version" and "neutron-sanity-check" on a CI node?

Re: [Openstack] Does anybody know something about ceph.com unavailability?!

2016-10-12 20:18 GMT+02:00 Erdősi Péter : > Hello! > > I know, it's not exactly OS question, but I think a lot of us using it with > libvirt, and maybe somebody have info, cause I cannot reach > download.ceph.com and ceph.com either for 3-4 days, and not found anything > about this

Re: [Openstack] [Devstack] How to configure SPICE local.conf

2016-09-19 15:50 GMT+02:00 Silvia Fichera : > Hi all, > I'm installing Openstack Mitaka via Devstack. > Since there is a bug in horizon (reported here > https://bugs.launchpad.net/horizon/+bug/1622684 ) Well, the bug is in noVNC really, you can work around it by checking

Re: [Openstack] [openstack][neutron] Why can't create network with vxlan type and physical network at the same time?

2016-09-06 11:17 GMT+02:00 James Guo : > In neutron, it is not permitted to create vxlan network with physical network > option > > In type_tunnel,py, the function validate_provider_aegment executes the > limitation. > > What is the consideration? Neutron has no way of

Re: [Openstack-operators] base/swap files are not created with use_cow_images=False

2016-08-29 11:01 GMT+02:00 Paul Dekkers : > > Hi, > > Since my fear of backing-file issues I've had years ago with live-migration I > always used: > > force_raw_images=False > use_cow_images=False > > ... on my compute nodes, to have qcow2 instances without backing file.

Re: [Openstack-operators] IPV6 help liberty

2016-07-13 18:01 GMT+02:00 suresh kumar : > Changed to SLAAC, instance failed to get metadata information and in logs I > don't see ip assigned to the instances, but when I logged into instance I > see ipv6 address. > > Do I need to update any metadata configuration?

Re: [Openstack-operators] IPV6 help liberty

2016-07-12 20:55 GMT+02:00 suresh kumar : > Hi All, > > I have created IPv6 vlan in neutron with DHCPv6 stateful option, when I > create instances with this ipv6 vlan dhcp is failing to assign the IP to > instances and it is assigning link local address > > I am able to ping

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

2016-06-22 9:18 GMT+02:00 Victor Stinner : > Hi, > > Current status: only 3 projects are not ported yet to Python 3: > > * nova (76% done) > * trove (42%) > * swift (0%) > >https://wiki.openstack.org/wiki/Python3 How should differences between python3.4 and python3.5 be

Re: [OpenStack-Infra] Correct URL to synch local pypi mirror from

2016-05-11 22:31 GMT+02:00 Bob Hansen : > Every few weeks my third part CI system gets burned by this. I have a > bandersnatch mirror, that mirrors from pypi.python.org every few hours, but > during a run it can't find packages that have been updated in various >

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

2016-04-27 12:43 GMT+02:00 Dhvanan Shah : > keystone --debug user-list gives this: > > /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65: > DeprecationWarning: The keystone CLI is deprecated in favor of > python-openstackclient. For a Python library, continue using >

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

2016-04-27 10:30 GMT+02:00 Dhvanan Shah : > UPDATE: > I am able to log into Horizon and perform all actions without any issue but > on my terminal, I am not able to do the same. The password that I thought > was wrong is not the issue as I logged in with the same password. > My

Re: [openstack-dev] [all] Python 3.5 is now the default Py3 in Debian Sid

2016-01-14 17:12 GMT+01:00 Thomas Goirand : > On 01/14/2016 11:35 PM, Yuriy Taraday wrote: >> >> >> On Thu, Jan 14, 2016 at 5:48 PM Jeremy Stanley > > wrote: >> >> On 2016-01-14 09:47:52 +0100 (+0100), Julien Danjou wrote: >>

Re: [openstack-dev] [diskimage-builder] disk-image-create from virtualenv not working

2015-07-02 19:58 GMT+02:00 Alec Hothan (ahothan) ahot...@cisco.com: I wonder if anybody else ran into the same issue as it looks like PyYAML is required on the native python in order for disk-image-crate to succeed. Installing PyYAML in a virtual environment and running disk-iage-create from

Re: [OpenStack-Infra] Nodepool for ubuntu vivid.

2015-06-05 3:49 GMT+02:00 Ian Wienand iwien...@redhat.com: On 06/05/2015 10:46 AM, Tony Breeds wrote: Hi All, I'd like to test the current dev release of ubuntu (15.04) in the gate. If I read nodepool.yaml.erb correctly then there currently isn't a nodepool image defined for this. That's a

Re: [openstack-dev] [nova][api] New micro-version needed for api bug fix or not?

2015-06-03 14:25 GMT+02:00 John Garbutt j...@johngarbutt.com: On 3 June 2015 at 12:52, Jay Pipes jaypi...@gmail.com wrote: On 06/03/2015 02:34 AM, Chris Friesen wrote: On 06/03/2015 12:16 AM, Jens Rosenboom wrote: I'm wondering though whether the current API behaviour here should be changed

Re: [openstack-dev] [nova][api] New micro-version needed for api bug fix or not?

2015-06-01 13:40 GMT+02:00 John Garbutt j...@johngarbutt.com: On 31 May 2015 at 14:15, Xu, Hejie hejie...@intel.com wrote: Replied in line with prefix [alex] -Original Message- ... 2) We also agreed that all micro version bumps need a spec, to help avoid is adding more bad things

[openstack-dev] [nova][api] New micro-version needed for api bug fix or not?

As the discussion in https://review.openstack.org/179569 still continues about whether this is just a bug fix, or an API change that will need a new micro version, maybe it makes sense to take this issue over here to the ML. My personal opinion is undecided, I can see either option as being

Re: [openstack-dev] Using DevStack in Kilo

2015-04-17 12:23 GMT+02:00 Sean Dague s...@dague.net: glanceclient has always been that way it's terrible. :( the nova message timeout looks like it's becauce nova-cert is not running, and it keeps trying to ping it. What actions were you doing that triggered that path? I think this

Re: [openstack-dev] [Nova][Neutron] Status of the nova-network to Neutron migration work

Am 01/04/15 um 04:10 schrieb Kevin Benton: It's worth pointing out here that the in-tree OVS solution controls traffic using iptables on regular bridges too. The difference between the two occurs when it comes to how traffic is separated into different networks. It's also worth noting that DVR

Re: [openstack-dev] [all] creating stable branches for all libraries, Oslo, client, and other

Am 24/03/15 um 22:22 schrieb Joe Gordon: On Tue, Mar 24, 2015 at 1:13 PM, Doug Hellmann d...@doughellmann.com wrote: We have a cross-project spec up for review discussing a change in the release process precipitated by the fact that we are now capping library versions in stable branch test

Re: [openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

Am 05/03/15 um 17:52 schrieb Doug Hellmann: On Thu, Mar 5, 2015, at 11:37 AM, Ian Cordasco wrote: The clients in general do not back port patches. Someone should work with stable-maint to raise the cap in Icehouse and Juno. I suspect, however, that those caps were added due to the client

Re: [openstack-dev] [Glance] [all] [stable] python-glanceclient release 0.16.1

? On 3/5/15, 10:28, Dr. Jens Rosenboom j.rosenb...@x-ion.de wrote: Am 05/03/15 um 06:02 schrieb Nikhil Komawar: The python-glanceclient release management team is pleased to announce: python-glanceclient version 0.16.1 has been released on Thursday, Mar 5th around 04:56 UTC. The release

Re: [Openstack-operators] How to force Heat to use v2.0 Keystone

Am 18/02/15 um 10:27 schrieb Alvise Dorigo: I had an error in the repository clone. Now I've successfully installed the plugin (python setup.py install). The backend is correctly configured in the heat.conf: [root@controller-02 ~]# grep keystone_backend /etc/heat/heat.conf

Re: [openstack-dev] [nova]nova not work with eventlet 0.16.0

Am 14/01/15 um 05:17 schrieb Adam Gandelman: So eventlet 0.16.x has started hitting slaves and breaking stable branches (its not like we weren't warned :\ ) https://bugs.launchpad.net/nova/+bug/1410626 Should hopefully be resolved by eventlet versions caps in icehouse + juno's requirements:

Re: [openstack-dev] [nova]nova not work with eventlet 0.16.0

Am 06/01/15 um 18:01 schrieb Daniel P. Berrange: On Tue, Jan 06, 2015 at 05:36:38PM +0100, Ihar Hrachyshka wrote: On 01/06/2015 05:33 PM, Daniel P. Berrange wrote: On Tue, Jan 06, 2015 at 10:21:10AM -0600, Matt Riedemann wrote: Odd...eventlet 0.16.0 was released on 12/30 and the eventlet.util

Re: [openstack-dev] Problem installing devstack

Am 06/01/15 um 04:40 schrieb Rajdeep Dua: Getting this error while running stack.sh in devstack Could not find a version that satisfies the requirement SQLAlchemy=0.8.99,=0.9.99,=0.8.4,=0.9.7 (from keystone==2014.2.dev114) (from versions: 0.4.2p3, 0.4.7p1, 0.5.4p1, 0.5.4p2, 0.1.0, 0.1.1, 0.1.2,

[openstack-dev] Git client vulnerability

As this may affect a reasonable percentage of the target audience, I would like to make everyone aware of https://github.com/blog/1938-vulnerability-announced-update-your-git-clients While github.com claim to have patched their servers, people using other repos may want to be extra cautious.