Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

+1 A lot of changes has been make in Mitaka. Backport is difficult. But using Mitaka deploy Liberty also has *much works*. For example, revert config file change which deprecated in Mitaka and Liberty support. A important one is the `keystone-manage bootstrap` command to create the keystone admi

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On 03/29/2016 08:33 PM, Doug Hellmann wrote: > If the core doc team isn't able to help you maintain it, maybe it's a > candidate for a separate guide, just like we're discussing for projects > that aren't part of the DefCore set included in the main guide. > > Doug This is exactly what I don't wa

[openstack-dev] [Senlin] Asking about launching an instance in Senlin cluster

Dear OpenStack Supporter, I am Cuong Nguyen, an Vietnamese IT engineer. Currently, I am researching about Senlin to apply for my work. I research to launch an virtual machine on a Senlin cluster. Could you please advice me to perform this action? If I am missing something, please let me know. Th

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

Michal, We can't commit to that. We discussed it at midcycle and unable to commit to it then. We are essentially abandoning the 1.0.0 release and replacing it with 1.1.0 because of the documentation outlined here: http://docs.openstack.org/developer/kolla/liberty-deployment-warning.html If we

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

From: Jeffrey Zhang mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Wednesday, March 30, 2016 at 12:29 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstac

Re: [openstack-dev] [all] Austin Design Summit track layout

John Dickinson wrote: On Thursday, I'd like to proposed swapping Swift's 1:30pm session with Fuel's 2:20pm session. This will give Swift a contiguous time block in the afternoon, and Fuel's session would line up right after their full morning (albeit after the lunch break). I have not had a c

Re: [openstack-dev] [all] Austin Design Summit track layout

Mark McClain wrote: Would it be possible to move the Astara fish bowl session to Thursday morning? It would avoid the conflict with Tacker. We’re hoping to see where the teams could cooperate across projects in the future. Yes, I'll move it to Thursday 9am, unless someone objects. -- Thier

Re: [openstack-dev] [all] Austin Design Summit track layout

Matt Riedemann wrote: On 3/29/2016 2:48 AM, Thierry Carrez wrote: Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's priority/scheduling talk in the last se

[openstack-dev] [OpenStack] "nova list" doesn't show networks for few instances

Hi, I am using OpenStack Juno on a multinode setup. When I did nova list I couldn't see any interfaces attached to few of my VMs although in Dashboard they are visible. -+ | ID | Name | Status | Task St

[openstack-dev] [Heat] Meeting time

Hi all, I'd like to be able to attend at least one of the IRC meeting, and it doesn't really work right now. So if you'd like to come to meetings, please fill the following doodle: http://doodle.com/poll/4m6aicfnwuug86rs Note that I'll try to make the best choice depending on my selfish availabil

Re: [openstack-dev] [Senlin] Asking about launching an instance in Senlin cluster

Hi Cuong, First you need to create a profile, and then create a cluster. There is some examples in senlin/example/profiles, you can start with this one https://github.com/openstack/senlin/blob/master/examples/profiles/cirros_basic/nova_server.yaml

[openstack-dev] [release][telemetry] Ceilometer Mitaka RC3 available

Due to a new release-critical issue spotted in Ceilometer during RC2 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/ceilometer/ceilometer-6.0.0.0rc3.tar.gz Unless new release-critical issues are found that wa

Re: [openstack-dev] [Openstack] [OpenStack] "nova list" doesn't show networks for few instances

Wrong user? Try --all-tenants and see what shows up as an admin Inviato da iPhone > Il giorno 30 mar 2016, alle ore 10:08, varun bhatnagar > ha scritto: > > Hi, > > I am using OpenStack Juno on a multinode setup. > When I did nova list I couldn't see any interfaces attached to few of my VMs

Re: [openstack-dev] [Heat] Meeting time

On Wed, Mar 30, 2016 at 10:13 AM, Thomas Herve wrote: > Hi all, > > I'd like to be able to attend at least one of the IRC meeting, and it > doesn't really work right now. So if you'd like to come to meetings, > please fill the following doodle: > http://doodle.com/poll/4m6aicfnwuug86rs The times

Re: [openstack-dev] "nova list" doesn't show networks for few instances

Do you use "2014.2.4" of Juno? If your OpenStack version is older than "2014.2.4", you might be hit the following bug. https://bugs.launchpad.net/nova/+bug/1407664 Rikimaru Honjo [email protected] On 2016/03/30 17:08, varun bhatnagar wrote: Hi, I am using OpenStack Juno on a mul

Re: [openstack-dev] [Openstack] [OpenStack] "nova list" doesn't show networks for few instances

Hello Remo, No, there is just one user "admin" and when I gave --all-tenants it returned the same output (without networks) BR, Varun On Wed, Mar 30, 2016 at 10:20 AM, Remo Mattei wrote: > Wrong user? > > Try --all-tenants and see what shows up as an admin > > Inviato da iPhone > > > Il giorno

Re: [openstack-dev] [neutron] unit test failures due to new release of Routes package (v2.3)

Aditya Vaja wrote: Hi, I'm seeing unit test failures when I test locally after a fresh git clone of neutron master. $ ./run_tests.sh -V -f Honestly, you should avoid using the script, and instead rely on tox. With tox, requirements are properly constrained, so you would not be hit by t

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

+1 On 30/03/16 04:27, Steven Dake (stdake) wrote: Dear cores, inc0 has been investigating our backport options for 1.1.0 and they look bleak. At this time we would have to backport heka because of changes in Docker 1.10.z which are incompatible with the syslog dev file. We had originally spok

Re: [openstack-dev] Nominating Vikram Hosakot for Core Reviewer

+1 -Original Message- From: Ryan Hallisey [mailto:[email protected]] Sent: Tuesday, March 29, 2016 6:40 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer +1 - Original Messa

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

+1 -Original Message- From: Paul Bourke [mailto:[email protected]] Sent: Wednesday, March 30, 2016 11:00 AM To: [email protected] Subject: Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch +1 On 30/03/16 04:27, Steven Dake

[openstack-dev] [fuel][plugins][ovs] NSH Query

Hi Folks, We were trying https://github.com/openstack/fuel-plugin-ovs.git, and has below query: *Our Setup:* SF | Classifier---SFF

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 -Original Message- From: Michal Rostecki [mailto:[email protected]] Sent: Wednesday, March 30, 2016 7:18 AM To: [email protected] Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer +1 _

Re: [openstack-dev] [all] Austin Design Summit track layout

On Wed, Mar 30, 2016 at 11:01 AM, Thierry Carrez wrote: > John Dickinson wrote: > >> On Thursday, I'd like to proposed swapping Swift's 1:30pm session with >> Fuel's 2:20pm session. This will give Swift a contiguous time block in the >> afternoon, and Fuel's session would line up right after thei

Re: [openstack-dev] [all] Austin Design Summit track layout

OpenStackClient, Stable and Release to a larger fishbowl room Cheers, -- Thierry Carrez (ttx) DSLayout-20160330.pdf Description: Adobe PDF document __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

[openstack-dev] [Fuel] [Openstack] Problem after reboot fuel-master VM

Hello, I have rebooted the "fuel-master" VM and after that, I cannot access the Fuel UI. What I am missing. Please check the image to see the error. Another question, How can I rediscover a node that was removed from the pool of available nodes, and also add new nodes to the pool. I clone a fu

Re: [openstack-dev] [fuel][plugins][ovs] NSH Query

Hi, Vikram ++ plugin authors explicitly On Wed, Mar 30, 2016 at 12:20 PM, Vikram Choudhary wrote: > Hi Folks, > > We were trying https://github.com/openstack/fuel-plugin-ovs.git, and has > below query: > > *Our Setup:* > SF >

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Hey Fuelers, I know that you probably wouldn't like to hear that, but in my opinion Fuel has to stop using Shotgun. It's nothing more but a command runner over SSH. Besides, it has well known issues such as retrieving remote directories with broken symlinks inside. So I propose to find a modern a

Re: [openstack-dev] [Fuel] [Openstack] Problem after reboot fuel-master VM

Hi, Samer It seems that Nailgun has not started. Could you please provide us with the version of Fuel you are using? You can find logs for nailgun in: for <9.0/pre-Mitaka versions /var/log//nailgun/ for current Mitaka: /var/log/nailgun/ On Wed, Mar 30, 2016 at 12:38 PM, Samer Machara < samer.m

[openstack-dev] [TripleO] Stable Branch policy for Liberty/Mitaka (revisited)

Hi all, Some time ago we had a discussion re $subject [1] which I want to revisit, because the stable/mitaka branches have now been created. That thread, and various IRC discussions have led to (I believe) the following consensus: 1. stable/mitaka will align with the normal stable/maint backport

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

FWIW, as a naive bystander: On 30/03/16 11:06, Igor Kalnitsky wrote: > Hey Fuelers, > > I know that you probably wouldn't like to hear that, but in my opinion > Fuel has to stop using Shotgun. It's nothing more but a command runner > over SSH. Besides, it has well known issues such as retrieving

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

+1 to discarding shotgun. Should we register a BP for that? > 30 бер. 2016 р. о 12:03 Igor Kalnitsky написав(ла): > > Hey Fuelers, > > I know that you probably wouldn't like to hear that, but in my opinion > Fuel has to stop using Shotgun. It's nothing more but a command runner > over SSH. Besi

[openstack-dev] [election][tc] Candidacy

Hi folks, I hereby announce my candidacy for the OpenStack Technical Committee election. Most of you probably know me by now, and for those who don't yet, let's say I've been around for almost 5 years now in the OpenStack community. I am currently acting as the PTL for Telemetry. I've been workin

Re: [openstack-dev] [Openstack-stable-maint][stable] Stable check of openstack/trove failed

Stable maintainers, I'm happy to fix in Kilo if required, the issue is Routes 2.3. It is a neat cherry-pick. Please advise. -amrith > -Original Message- > From: A mailing list for the OpenStack Stable Branch test reports. > [mailto:[email protected]] > Sent: We

Re: [openstack-dev] [Fuel] [Openstack] Problem after reboot fuel-master VM

Hi Vladimir, I'm using fuel 7.0, Which log I need to see? - Original Message - From: " Vladimir Kuklin vkuklin at mirantis.com To: "OpenStack Development Mailing List" Sent: Wed Mar 30 10:06:22 UTC 2016 Subject: [Fuel] [Openstack] Problem after reboot fuel-master VM Hi, Samer It se

Re: [openstack-dev] [Fuel] [Openstack] Problem after reboot fuel-master VM

Thanks, Problem solved by magic. It looks like, the nailgun service take some time to start up in my computer. - Original Message - From: "Samer Machara" To: "OpenStack Development Mailing List" Sent: Wednesday, March 30, 2016 12:39:35 PM Subject: Re: [Fuel] [Openstack] Problem af

Re: [openstack-dev] [fuel] Component Leads Elections

Dmitry, "No need to rush" does not mean we should postpone team structure changes until Ocata. IMO, CL role (when it is exposed to Fuel) contradicts to our modularization activities. Fuel should be an aggregator of components. What if we decide to use Ironic or Neutron as Fuel components? Should w

Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

Seems like the explanation below indeed suggests that’s a regression for Mitaka. We’ll track the bug for a backport. I don’t think that we can block the initial Mitaka release for that though. So let’s work on the master fix right now, and target the fix for Mitaka for one of the first minor

[openstack-dev] [telemetry] Rescheduling IRC meetings

Hi folks, I've recently noticed that our way of collaborating is now mostly done asynchronously through Gerrit and the mailing list. Which is good since it's easy for everyone to participate. Some synchronous discussion happens in #openstack-telemetry, which is also a good thing since it's a handy

Re: [openstack-dev] [Fuel] [Openstack] Problem after reboot fuel-master VM

Samer my 2c are: after Fuel node reboot just run 'docker ps -a' to get information if all containers have been already running. On Wed, Mar 30, 2016 at 1:07 PM, Samer Machara < [email protected]> wrote: > Thanks, >Problem solved by magic. It looks like, the nailgun service t

[openstack-dev] [trove] Trove team meeting today, 1800 UTC, #openstack-meeting-alt

We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt Meeting agenda is at https://wiki.openstack.org/wiki/Meetings/TroveMeeting We have a lengthy agenda for today so please review ahead of time. -amrith ___

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

On Wed, 30 Mar 2016, Julien Danjou wrote: Thoughts? +1 I especially agree that asynch (gerrit and email) interaction is far more accessible and productive. Another option on the meetings would be to do what the cross project meetings do: Only have the meeting if there are agenda items. -- C

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

On Wed, Mar 30 2016, Chris Dent wrote: > Another option on the meetings would be to do what the cross project > meetings do: Only have the meeting if there are agenda items. That's a good idea, I'd be totally cool with that too. We could send a mail indicating there would be meeting with a 1 week

Re: [openstack-dev] [neutron] unit test failures due to new release of Routes package (v2.3)

Also: https://review.openstack.org/298482 and it's children in stable/xyz Thanks to Henry for helping review the Trove changes for this issue. -amrith > -Original Message- > From: Henry Gessau [mailto:[email protected]] > Sent: Tuesday, March 29, 2016 9:05 PM > To: OpenStack Developmen

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Neil Jerram wrote: > But isn't Ansible also over-complicated for just running commands over SSH? It may be not so "simple" to ignore that. Ansible has a lot of modules which might be very helpful. For instance, Shotgun makes a database dump and there're Ansible modules with the same functionality

[openstack-dev] [release][all] What is upper-constraints.txt?

Folks, Quick primer/refresh because of some gate/CI issues we saw last few days with Routes===2.3 upper-constraints.txt is the current set of all the global libraries that should be used by all the CI jobs. This file is in the openstack/requirements repo: http://git.openstack.org/cgit/openstack/

Re: [openstack-dev] [Fuel] [Openstack] Problem after reboot fuel-master VM

Samer, you could always use `dockerctl check all|` command. On Wed, Mar 30, 2016 at 2:47 PM, Adam Heczko wrote: > Samer my 2c are: > after Fuel node reboot just run 'docker ps -a' to get information if all > containers have been already running. > > On Wed, Mar 30, 2016 at 1:07 PM, Samer Machara

[openstack-dev] [neutron] PBAM Extension RFE

I recently added a Neutron RFE [1] that proposes a new extension called Pluggable Backend Association Mappings (PBAM). This admin-based extension allows consumers to view Neutron / backend resource mappings, quickly identify mappings that are out of sync and remediate them. If this sounds interest

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

On 30/03/16 13:35, Igor Kalnitsky wrote: > Neil Jerram wrote: >> But isn't Ansible also over-complicated for just running commands over SSH? > > It may be not so "simple" to ignore that. Ansible has a lot of modules > which might be very helpful. For instance, Shotgun makes a database > dump and th

Re: [openstack-dev] [release][all] What is upper-constraints.txt?

On 2016-03-30 14:33, Davanum Srinivas wrote: > Folks, > > Quick primer/refresh because of some gate/CI issues we saw last few > days with Routes===2.3 > > upper-constraints.txt is the current set of all the global libraries > that should be used by all the CI jobs. We're not ready yet for such a

[openstack-dev] [release][all][ptls] the plan for the final week of the Mitaka release

Folks, We are approaching the final week of the Mitaka release cycle, and the release team wants to make sure everyone is clear about what will be happening and what the policies for changes are. First, a few dates: * Tomorrow 31 March is the final day for requesting release candidates for pr

Re: [openstack-dev] [release][all] What is upper-constraints.txt?

On Wed, Mar 30, 2016 at 08:33:06AM -0400, Davanum Srinivas wrote: > Folks, > > Quick primer/refresh because of some gate/CI issues we saw last few > days with Routes===2.3 > > upper-constraints.txt is the current set of all the global libraries > that should be used by all the CI jobs. > > This

Re: [openstack-dev] [magnum] Discuss the blueprint "support-private-registry"

Hi. On Wed, Mar 30, 2016 at 3:59 AM, Eli Qiao wrote: > > Hi Hongbin > > Thanks for starting this thread, > > > > I initial propose this bp because I am in China which is behind China great > wall and can not have access of gcr.io directly, after checking our > cloud-init script, I see that > > lo

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

​Igor, I can not agree more. Wherever possible we should use existent mature solutions. Ansible is really convenient and well known solution, let's try to use it. Yet another thing should be taken into account. One of Shotgun features is diagnostic report that could then be attached to bugs to id

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

On 30/03/2016 8:06 AM, Julien Danjou wrote: > On Wed, Mar 30 2016, Chris Dent wrote: > >> Another option on the meetings would be to do what the cross project >> meetings do: Only have the meeting if there are agenda items. > > That's a good idea, I'd be totally cool with that too. We could send

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Wed, Mar 30, 2016, at 03:37 AM, Thomas Goirand wrote: > On 03/29/2016 08:33 PM, Doug Hellmann wrote: > > If the core doc team isn't able to help you maintain it, maybe it's a > > candidate for a separate guide, just like we're discussing for projects > > that aren't part of the DefCore set inc

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

Gal, Thursday 4:10 – 4:50 conflicts with a Magnum workroom session, but we can choose from: · 11:00 – 11:40 · 11:50 – 12:30 · 3:10 – 3:50 Please let us know if some of the slots don’t work well with your schedule. Best regards, Hongbin From: Gal Sagie [mailto:gal.sa.

[openstack-dev] Mitaka RC packages for openSUSE and SLES available

Hi, In the last few weeks we've been working hard on stabilizing the Mitaka packages, and the packages currently available in Cloud:OpenStack:Mitaka [0] pass early testing. Feel free to try them out by adding the repository: http://download.opensuse.org/repositories/Cloud:/OpenStack:/Mitaka/$DI

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Osquery [1] could also be considered as providing a lot of useful informations in a convenient way. [1] https://osquery.io/ On Wed, Mar 30, 2016 at 3:20 PM, Vladimir Kozhukalov < [email protected]> wrote: > ​Igor, > > I can not agree more. Wherever possible we should > use existent matur

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Hi, Do we have any requirements for the new tool? Do we know what we don’t like about current implementation, what should be avoided, etc.? Before that we can only speculate. From my ops experience, shotgun like tools will not work conveniently on medium to big environments. Even on medium env

Re: [openstack-dev] [magnum] Discuss the blueprint"support-private-registry"

I agree to that support-private-registry should be secure. As insecure seems not much useful for production use. Also I understood the point setup related CA could be diffcult than normal HTTP, but we want to know if https://blueprints.launchpad.net/magnum/+spec/allow-user-softwareconfig Could add

Re: [openstack-dev] [release][all] What is upper-constraints.txt?

> -Original Message- > From: Jim Rollenhagen [mailto:[email protected]] > Sent: Wednesday, March 30, 2016 9:01 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [release][all] What is upper-constraints.txt? > > On Wed, Mar 30, 201

Re: [openstack-dev] [release][all] What is upper-constraints.txt?

> -Original Message- > From: Andreas Jaeger [mailto:[email protected]] > Sent: Wednesday, March 30, 2016 9:03 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [release][all] What is upper-constraints.txt? > > On 2016-03-30 14:33, Davanum S

Re: [openstack-dev] [kloudbuster] authorization failed problem

Hi Alec, Thanks for clarifying. I didnot have the cinder service previously. It was not a complete setup. Now, I did the setup of cinder service. Output of keystone service list. [image: Inline image 1] I installed the setup of openstack using the installation guide for ubuntu and for kloudbuster,

Re: [openstack-dev] [all] Austin Design Summit track layout

Sylvain Bauza wrote: Le 29/03/2016 09:48, Thierry Carrez a écrit : Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's priority/scheduling talk in the last

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

All these slots are fine with me, added Kuryr team as CC to make sure most can attend any of these times. On Wed, Mar 30, 2016 at 5:12 PM, Hongbin Lu wrote: > Gal, > > > > Thursday 4:10 – 4:50 conflicts with a Magnum workroom session, but we can > choose from: > > · 11:00 – 11:40 > > ·

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

Another use case I can think of is to cache the required docker images in the Glance image. This is an important use case because we have containerized most of the COE components (e.g. kube-scheduler, swarm-manager, etc.). As a result, each bay needs to pull docker images over the Internet on p

Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

On 29/03/16 20:42, Miguel Lavalle wrote: > Hi, Hi Miguel, > I am writing a patchset to build a mapping between hosts and network > segments. The goal of this mapping is to be able to say whether a host > has access to a given network segment. I am building this mapping > assuming that if a host A

Re: [openstack-dev] [magnum] Discuss the blueprint"support-private-registry"

Hi. On Wed, Mar 30, 2016 at 4:20 PM, Kai Qiang Wu wrote: > I agree to that support-private-registry should be secure. As insecure > seems not much useful for production use. > Also I understood the point setup related CA could be diffcult than normal > HTTP, but we want to know if > https://blue

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

On Wed, Mar 30, 2016 at 7:57 AM, Chris Dent wrote: > On Wed, 30 Mar 2016, Julien Danjou wrote: > >> Thoughts? > > > +1 > > I especially agree that asynch (gerrit and email) interaction is far > more accessible and productive. > > Another option on the meetings would be to do what the cross project

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On 12.02.2016 15:01, Ihar Hrachyshka wrote: > Salvatore Orlando wrote: > >> On 11 February 2016 at 20:17, John Belamaric >> wrote: >> >>> On Feb 11, 2016, at 12:04 PM, Armando M. wrote: >>> >>> >>> >>> On 11 February 2016 at 07:01, John Belamaric >>> wrote: >>> >>> >>> >>> It is only internal i

[openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

Intel has a few third party CIs in the third party systems wiki [1]. I was talking with Moshe Levi today about expanding coverage for mellanox CI in nova, today they run an SRIOV CI for vnic type 'direct'. I'd like them to also start running their 'macvtap' CI on the same nova changes (that jo

Re: [openstack-dev] [all] Austin Design Summit track layout

Ihar Hrachyshka wrote: I'd then have the same problem than Matt here as I'm the Release CPL for Nova. That said, given I think I'm the only person probably having the issue, I can say fair enough and try to clone myself before the Summit :-) Actually, now that I am a release CPL for Neutron, as

[openstack-dev] [magnum][magnum-ui] Have magnum jobs respect upper-constraints.txt

Hi team, After a quick check, it seems python-magnumclient and magnum-ui don't use upper constraints. Magnum (the main repo) uses upper constraints in integration tests (gate-functional-*), but doesn't use it in others (e.g. py27, py34, pep8, docs, coverage). The missing of upper constraints co

[openstack-dev] [Fuel] Extra red tape for filing bugs

Guys, I’m not trying to be a foreteller but with a bug template this huge and complicated people will either not follow it or track bugs somewhere else. Perhaps we should make it simpler? Detailed bug description: Steps to reproduce: Expected results: Actual result: Reproducibility: W

Re: [openstack-dev] [Fuel] Extra red tape for filing bugs

We also often use bugtracker as a TODO tracker. This template does not work for TODOs at all. I understand that it’s not technically mandatory to follow it, but if that Fuel Bug Checker is going to spam on every single TODO, our inboxes will overflow. > 30 бер. 2016 р. о 17:37 Roman Prykhodchen

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

On 11/03/16 23:20, Carl Baldwin wrote: > Hi, Hi Carl, and sorry for the lateness of this reply. > I have started to get into coding [1] for the Neutron routed networks > specification [2]. > > This spec proposes a new association between network segments and > subnets. This affects how IPAM need

Re: [openstack-dev] [all] Austin Design Summit track layout

Thierry Carrez wrote: Ihar Hrachyshka wrote: I'd then have the same problem than Matt here as I'm the Release CPL for Nova. That said, given I think I'm the only person probably having the issue, I can say fair enough and try to clone myself before the Summit :-) Actually, now that I am a re

Re: [openstack-dev] [magnum][magnum-ui] Have magnum jobs respect upper-constraints.txt

On 03/30/2016 05:31 PM, Hongbin Lu wrote: > Hi team, > > After a quick check, it seems python-magnumclient and magnum-ui don't use > upper constraints. Magnum (the main repo) uses upper constraints in > integration tests (gate-functional-*), but doesn't use it in others (e.g. > py27, py34, pep8

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

On 29/03/16 19:16, Carl Baldwin wrote: > I've been playing with this a bit on this patch set [1]. I haven't > gotten very far yet but it has me thinking. > > Calico has a similar use case in mind as I do. Essentially, we both > want to group subnets to allow for aggregation of routes. (a) In > r

Re: [openstack-dev] [magnum][magnum-ui] Have magnum jobs respect upper-constraints.txt

Thanks Hongbin, I've updated the bug summary to be more generic. -amrith > -Original Message- > From: Hongbin Lu [mailto:[email protected]] > Sent: Wednesday, March 30, 2016 11:32 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [magn

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

On 29/03/16 21:55, Carl Baldwin wrote: > > I thought of another type of grouping which could benefit pluggable > IPAM today. It occurred to me as I was refreshing my memory on how > pluggable IPAM works when there are multiple subnets on a network. > Currently, Neutron's backend pulls the subnets

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On 30/03/16 16:08, Pavel Bondar wrote: > We are now in early Newton, so it is good time to discuss plan for > pluggable ipam for this release cycle. > > Kevin Benton commented on review page for current migration to pluggable > approach [1]: >> >> IMO this cannot be optional. It's going to be a ni

Re: [openstack-dev] [all] Austin Design Summit track layout

Yes, I checked on that. Based on where in the schedule that is, and based on the way we're planning on doing the working sessions, it will be just fine for me to not be in that particular session. It's much better for the community that we have the contiguous block that I personally be present i

Re: [openstack-dev] [all] Austin Design Summit track layout

On 3/30/2016 10:42 AM, Ihar Hrachyshka wrote: Thierry Carrez wrote: Ihar Hrachyshka wrote: I'd then have the same problem than Matt here as I'm the Release CPL for Nova. That said, given I think I'm the only person probably having the issue, I can say fair enough and try to clone myself bef

Re: [openstack-dev] [all] Austin Design Summit track layout

John Dickinson wrote: Yes, I checked on that. Based on where in the schedule that is, and based on the way we're planning on doing the working sessions, it will be just fine for me to not be in that particular session. It's much better for the community that we have the contiguous block that I

Re: [openstack-dev] [Rally] single router per tenant in network context

Hi Aleksandr, Thanks Aleksandr. According to your references,I made the necessary changes to the code for single router , but now facing problems in the resource cleanup. While I correct the code, Can you suggest how to generate traffic between the VMs ? Is there any tool that is generally used for

Re: [openstack-dev] [all] Austin Design Summit track layout

Matt Riedemann wrote: 1:30pm on Thursday (first slot after lunch is unconference for nova) would work for me. OK, I'll make that swap too (unless Josh hits me with a trout over the night) -- Thierry Carrez (ttx) __ Open

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On Wed, Mar 30, 2016 at 9:03 AM, Pavel Bondar wrote: > Kevin Benton commented on review page for current migration to pluggable > approach [1]: > > IMO this cannot be optional. It's going to be a nightmare to try to support > two IPAM systems that people may have switched between at various points

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

On Wed, Mar 30, 2016 at 3:52 AM, Steven Dake (stdake) wrote: > > > From: Jeffrey Zhang > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > > Date: Wednesday, March 30, 2016 at 12:29 AM > To: "OpenStack Development Mailing List (not for usage questions)" > > Subject: Re:

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

On 03/30/2016 09:51 AM, Steven Dake (stdake) wrote: Michal, We can't commit to that. We discussed it at midcycle and unable to commit to it then. We are essentially abandoning the 1.0.0 release and replacing it with 1.1.0 because of the documentation outlined here: http://docs.openstack.org/d

Re: [openstack-dev] Fw:Extending API via Plugins

Hi wangzhh, I think this look reasonable, but I would prefer to have a proper spec for this feature. I generally like to have extendable API in Murano. On Thu, Mar 24, 2016 at 8:49 PM, 王正浩 wrote: > I'm sorry that I forgot to tell you murano-paste.ini should be modified to > ... > [app:apiv1app]

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

Agreed this needs to happen +1, - Original Message - From: "Jeff Peeler" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Wednesday, March 30, 2016 1:22:31 PM Subject: Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch O

Re: [openstack-dev] [Fuel] [RDO] Volunteers needed

Hi, Vladimir, this is a great feature, which can make Fuel truly universal. But i think it is hard to fully commit to the whole thing at once, especially for new contributors. Let's start with splitting it into some observable chunks of work, in a form of wiki page, blueprint or spec. This way it

Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

Bob, Thanks for your detailed response. In it you "strongly recommend that any functionality trying to make decisions based on connectivity do so by calling into the registered mechanism drivers, so they can decide whether whatever they manage has connectivity". After eading this I went through th

Re: [openstack-dev] [kloudbuster] authorization failed problem

Hi, Akshay, From the log you attached, the good news is you got KloudBuster installed and running fine! The problem is the image you are using (v5) is outdated for the latest KloudBuster main code. ☺ Normally for every version of KloudBuster, it needs certain version of image to support the fu

Re: [openstack-dev] [i18n][horizon][sahara][trove][magnum][murano] dashboard plugin release schedule

Just an update on this thread that the trove-dashboard RC2 was released https://review.openstack.org/#/c/298365/ Thanks, Craig Vyvial On Wed, Mar 23, 2016 at 11:36 PM Craig Vyvial wrote: > The trove-dashboard has its own stable/mitaka branch [1] as well. We have > an RC1 release already and we

Re: [openstack-dev] [kloudbuster] authorization failed problem

Hi Yichen, Thanks a lot . I will try with v6 and reach out to you for further help. Regards, Akshay On Wed, Mar 30, 2016 at 11:35 PM, Yichen Wang (yicwang) wrote: > Hi, Akshay, > > > > From the log you attached, the good news is you got KloudBuster installed > and running fine! The problem is t

Re: [openstack-dev] [TripleO] tripleo-quickstart import

On Tue, Mar 29, 2016 at 08:30:22PM -0400, John Trowbridge wrote: > Hola, > > With the approval of the tripleo-quickstart spec[1], it is time to > actually start doing the work. The first work item is moving it to the > openstack git. The spec talks about moving it as is, and this would > still be

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

So I made this: https://review.openstack.org/#/c/299563/ I'm not super fond of reverting commits from the middle of release, because this will make a lot of mess. I'd rather re-implement keystone bootstrap logic and make it conditional as it is not that complicated. On 30 March 2016 at 12:37, Rya

[openstack-dev] minutes of the Trove meeting 2016-03-30

Meeting minutes can be found at http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-03-30-18.01.txt Thanks to all who attended. -amrith __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: o

  1   2   >