Re: [openstack-dev] os-*-config in tripleo repositories

Excerpts from Dan Prince's message of 2014-01-09 11:56:16 -0700: > > - Original Message - > > From: "Derek Higgins" > > To: "OpenStack Development Mailing List" > > Sent: Thursday, January 9, 2014 8:13:53 AM > > Subject: [openstack-dev] os-*-config in tripleo repositories > > > > It loo

Re: [openstack-dev] Implementing VPNaas in Openstack Grizzly release

Hi Paul, Thanks for the info provided. There is IPSEC_AGENT_TOPIC defined and that is imported in service_driver/ipsec.py. Code is present. As I have not installed Openstack Grizzly set up using devstack, I do not have access to q-vpn process log. So if the RPC is timing out waiting for the resp

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On 2014?01?10? 00:49, Robert Li (baoli) wrote: Hi Folks, HI, all basiclly i flavor the pic-flavor style and against massing the white-list. please see my inline comments. With John joining the IRC, so far, we had a couple of productive meetings in an effort to come to consensus and m

Re: [openstack-dev] [wsme] Undefined attributes in WSME

On Thu, 2014-01-09 at 11:16 +0100, Julien Danjou wrote: > On Thu, Jan 09 2014, Jamie Lennox wrote: > > > Is there any way to have WSME pass through arbitrary attributes to the > > created object? There is nothing that i can see in the documentation or code > > that would seem to support this. > >

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

BTW, I like the PCI flavor :) From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com] Sent: Thursday, January 09, 2014 10:41 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support Hi, Ian, when you in aggrem

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi, Ian, when you in aggrement with all of this, do you agree with the 'group name', or agree with John's pci flavor? I'm against the PCI group and will send out a reply later. --jyh From: Ian Wells [mailto:ijw.ubu...@cack.org.uk] Sent: Thursday, January 09, 2014 9:47 AM To: OpenStack Developmen

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Robert, sorry that I'm not fan of * your group * term. To me, *your group" mixed two thing. It's an extra property provided by configuration, and also it's a very-not-flexible mechanism to select devices (you can only select devices based on the 'group name' property). 1) A dynamic group

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

- Original Message - > > The UI will also need to be able to look at the Heat resources running > > within the overcloud stack and classify them according to a resource > > category. How do you envision that working? > > There's a way in a Heat template to specify arbitrary metadata on a

Re: [openstack-dev] [Neutron][qa]API testing update

Sukhdev, API tests are really not for end-to-end testing; also, tempest tests (both API and scenario) should not make any assumptions about neutron configuration (e.g. ml2 mechanism drivers). End-to-end testing for particular ml2 drivers seems to fit in 3rd party testing where you can run addition

[openstack-dev] [Neutron] Service VM: Meeting on framework for advanced service

Hello Neutron developers. Framework for advanced service[1][2] was discussed at the last summit. Since it's been a while and there has been a progress as the code[3], I think it's good time to brain storm/discuss on it in face-to-face manner. So I'm arranging it. If you'd like to attend, please co

Re: [openstack-dev] Devstack on Fedora 20

On 01/09/2014 04:58 PM, Sean Dague wrote: On 01/09/2014 04:12 PM, Dean Troyer wrote: On Thu, Jan 9, 2014 at 2:16 PM, Adam Young mailto:ayo...@redhat.com>> wrote: That didn't seem to make a difference, still no cache. The RPMS are not getting installed, even if I deliberately add a li

Re: [openstack-dev] [nova] Discuss the option delete_on_termination

Hi lingguo: Maybe you could go to IRC to look for some comments/feedbacks, some Cores should be right there. Hope you can hear opinions on this before putting more efforts in resolving this . 2014/1/8 黎林果 > Hi All, > >Attach a volume when creating a server, the API contains > 'block_device

[openstack-dev] [ ceilometer] The Pagination patches

Hi, all, Since we still have no new conclusion for pagination for now, shall we still go on with the current pagination solution? Please help to review patches: https://review.openstack.org/#/c/41869/ https://review.openstack.org/#/c/35454/ May be we can work on this two first:). There are still

[openstack-dev] [Nova] Detect changes in object model

Hi Dan, There is a discussion in https://review.openstack.org/#/c/58199/ talking about the change detection in objects. If an object A contains another object or object list (called sub-object), any change happened in the sub-object can't be detected by obj_what_changed() in object A. A generi

Re: [openstack-dev] os-*-config in tripleo repositories

On 10 January 2014 02:13, Derek Higgins wrote: > It looks like we have some duplication and inconsistencies on the 3 > os-*-config elements in the tripleo repositories > > os-apply-config (duplication) : >We have two elements that install this > diskimage-builder/elements/config-applier/

Re: [openstack-dev] [nova][turbo hipster] unable to rebase

Hi! Sorry the slow response. I've been at a conference this week, so I'm a bit behind. I apologise for that. The root cause here is a failure to understand the relatively undocumented git behaviour of zuul. We think we've now got a fix, and will deploy it soon. Michael On Thu, Jan 9, 2014 at 8

Re: [openstack-dev] Less option (was: [oslo.config] Centralized config management)

On Thu, Jan 9, 2014 at 3:01 PM, Jay Pipes wrote: > On Thu, 2014-01-09 at 23:56 +0100, Julien Danjou wrote: > > On Thu, Jan 09 2014, Jay Pipes wrote: > > > > > Hope you don't mind, I'll jump in here :) > > > > > > On Thu, 2014-01-09 at 11:08 -0800, Nachi Ueno wrote: > > >> Hi Jeremy > > >> > > >>

Re: [openstack-dev] [Solum][Pecan][Security] Pecan SecureController vs. Nova policy

Hi Rayan, Thank you for sharing your view on SecureController. That is always good to hear info from the developers who are deeply familiar with the code base. I like an idea with hooks. If we go this path, we will need to have an information about a method of a particular controller which will b

Re: [openstack-dev] os-*-config in tripleo repositories

On Thu, Jan 9, 2014 at 1:56 PM, Dan Prince wrote: > I'm not the biggest fan of having multiple venv's for each component though. > Especially now that we have a global requirements.txt file where we can > target a common baseline. Multiple venvs causes lots of duplicated libraries > and increas

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

I'm in! Is the day Jan 27th? On Fri, Jan 10, 2014 at 6:33 AM, Anita Kuno wrote: > On 01/10/2014 02:53 AM, Jay Pipes wrote: >> On Thu, 2014-01-09 at 07:46 -0500, Sean Dague wrote: >>> I think we are all agreed that the current state of Gate Resets isn't >>> good. Unfortunately some basic functiona

Re: [openstack-dev] [oslo.config] Centralized config management

2014/1/9 Doug Hellmann : > > > > On Thu, Jan 9, 2014 at 3:56 PM, Nachi Ueno wrote: >> >> Hi Oleg >> >> 2014/1/9 Oleg Gelbukh : >> > On Fri, Jan 10, 2014 at 12:18 AM, Nachi Ueno wrote: >> >> >> >> 2014/1/9 Jeremy Hanmer : >> >> >> >> > How do you see these interactions defined? For instance, if I

Re: [openstack-dev] [nova][documentation][devstack] Confused about how to set up a Nova development environment

On Thu, Jan 9, 2014 at 12:21 PM, Mike Spreitzer wrote: > Brant Knudson wrote on 01/09/2014 10:07:27 AM: > > > > When I was starting out, I ran devstack ( > http://devstack.org/ ) on > > an Ubuntu VM. You wind up with a system where you've got a basic > > running OpenStack so you can try things o

Re: [openstack-dev] Less option (was: [oslo.config] Centralized config management)

On Thu, 2014-01-09 at 23:56 +0100, Julien Danjou wrote: > On Thu, Jan 09 2014, Jay Pipes wrote: > > > Hope you don't mind, I'll jump in here :) > > > > On Thu, 2014-01-09 at 11:08 -0800, Nachi Ueno wrote: > >> Hi Jeremy > >> > >> Don't you think it is burden for operators if we should choose corr

[openstack-dev] Less option (was: [oslo.config] Centralized config management)

On Thu, Jan 09 2014, Jay Pipes wrote: > Hope you don't mind, I'll jump in here :) > > On Thu, 2014-01-09 at 11:08 -0800, Nachi Ueno wrote: >> Hi Jeremy >> >> Don't you think it is burden for operators if we should choose correct >> combination of config for multiple nodes even if we have chef and

[openstack-dev] Reg vxlans configuration in Neutron

Hi, I am trying to use vxlans in Havana. I have two nodes, one acting as controller+network node and other as compute node. VM's launched have not got the dhcp ip. I have compiled openvswitch from openvswitch-2.0.0 tar ball and installed both userspace and kmod rpms. modinfo openvswitch filenam

Re: [openstack-dev] [oslo.config] Centralized config management

On Thu, Jan 9, 2014 at 3:56 PM, Nachi Ueno wrote: > Hi Oleg > > 2014/1/9 Oleg Gelbukh : > > On Fri, Jan 10, 2014 at 12:18 AM, Nachi Ueno wrote: > >> > >> 2014/1/9 Jeremy Hanmer : > >> > >> > How do you see these interactions defined? For instance, if I deploy > >> > a custom driver for Neutron,

Re: [openstack-dev] [Solum][Pecan][Security] Pecan SecureController vs. Nova policy

As a Pecan developer, I’ll chime in and say that I’m actually *not* a fan of SecureController and its metaclass approach. Maybe it’s just too magical for my taste. I’d give a big thumbs up to an approach that involves utilizing pecan’s hooks. Similar to Kurt’s suggestion with middleware, they

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

- Original Message - > On Thu, 2014-01-09 at 16:02 -0500, Tzu-Mainn Chen wrote:> There are a > number of other models in the tuskar code[1], do we need to > > > consider these now too? > > > > > > [1]: > > > https://github.com/openstack/tuskar/blob/master/tuskar/db/sqlalchemy/models.py >

Re: [openstack-dev] Devstack on Fedora 20

On 01/09/2014 04:12 PM, Dean Troyer wrote: > On Thu, Jan 9, 2014 at 2:16 PM, Adam Young > wrote: > > That didn't seem to make a difference, still no cache. The RPMS are > not getting installed, even if I deliberately add a line for > python-dogpile-cache >

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On 9 January 2014 22:50, Ian Wells wrote: > On 9 January 2014 20:19, Brian Schott wrote: > On the flip side, vendor_id and product_id might not be sufficient. > Suppose I have two identical NICs, one for nova internal use and the > second for guest tenants? So, bus numbering may be required. >

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On 9 January 2014 20:19, Brian Schott wrote: > Ian, > > The idea of pci flavors is a great and using vendor_id and product_id make > sense, but I could see a case for adding the class name such as 'VGA > compatible controller'. Otherwise, slightly different generations of > hardware will mean cust

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

On Thu, 2014-01-09 at 16:02 -0500, Tzu-Mainn Chen wrote:> There are a number of other models in the tuskar code[1], do we need to > > consider these now too? > > > > [1]: > > https://github.com/openstack/tuskar/blob/master/tuskar/db/sqlalchemy/models.py > > Nope, these are gone now, in favor of T

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

On 01/10/2014 02:53 AM, Jay Pipes wrote: > On Thu, 2014-01-09 at 07:46 -0500, Sean Dague wrote: >> I think we are all agreed that the current state of Gate Resets isn't >> good. Unfortunately some basic functionality is really not working >> reliably, like being able to boot a guest to a point wh

Re: [openstack-dev] [nova][neutron] top gate bugs: a plea for help

On 01/08/2014 05:53 PM, Joe Gordon wrote: > Hi All, > > As you know the gate has been in particularly bad shape (gate queue over > 100!) this week due to a number of factors. One factor is how many major > outstanding bugs we have in the gate. Below is a list of the top 4 open > gate bugs. > >

Re: [openstack-dev] Devstack on Fedora 20

On Thu, Jan 9, 2014 at 2:16 PM, Adam Young wrote: > That didn't seem to make a difference, still no cache. The RPMS are not > getting installed, even if I deliberately add a line for > python-dogpile-cache > Shouldn't it get installed via pip without the rpm line? > Yes pip should install it b

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi, One use case was brought up in today's meeting that I think is not valid. It is the use case where all 3 vnic types : Virtio, direct and macvtap (the terms used in the meeting were slow, fast, faster/foobar) could be attached to the same VM. The main difference between a direct and mac

Re: [openstack-dev] [oslo.config] Centralized config management

Hi Oleg 2014/1/9 Oleg Gelbukh : > On Fri, Jan 10, 2014 at 12:18 AM, Nachi Ueno wrote: >> >> 2014/1/9 Jeremy Hanmer : >> >> > How do you see these interactions defined? For instance, if I deploy >> > a custom driver for Neutron, does that mean I also have to patch >> > everything that will be tal

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

- Original Message - > I'm glad we are hashing this out as I think there is still some debate > around if Tuskar will need a database at all. > > One thing to bear in mind, I think we need to make sure the terminology > matches that described in the previous thread. I think it mostly doe

Re: [openstack-dev] [oslo.config] Centralized config management

Hi Jay 2014/1/9 Jay Pipes : > Hope you don't mind, I'll jump in here :) I'll never mind to discuss with you :) > On Thu, 2014-01-09 at 11:08 -0800, Nachi Ueno wrote: >> Hi Jeremy >> >> Don't you think it is burden for operators if we should choose correct >> combination of config for multiple nod

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

I'm glad we are hashing this out as I think there is still some debate around if Tuskar will need a database at all. One thing to bear in mind, I think we need to make sure the terminology matches that described in the previous thread. I think it mostly does here but I'm not sure the Tuskar mo

Re: [openstack-dev] [oslo.config] Centralized config management

On Fri, Jan 10, 2014 at 12:18 AM, Nachi Ueno wrote: > 2014/1/9 Jeremy Hanmer : > > How do you see these interactions defined? For instance, if I deploy > > a custom driver for Neutron, does that mean I also have to patch > > everything that will be talking to it (Nova, for instance) so they can

Re: [openstack-dev] [oslo.config] Centralized config management

Hope you don't mind, I'll jump in here :) On Thu, 2014-01-09 at 11:08 -0800, Nachi Ueno wrote: > Hi Jeremy > > Don't you think it is burden for operators if we should choose correct > combination of config for multiple nodes even if we have chef and > puppet? It's more of a burden for operators

Re: [openstack-dev] [oslo.config] Centralized config management

Hi Bob 2014/1/9 Robert Kukura : > On 01/09/2014 02:34 PM, Nachi Ueno wrote: >> Hi Doug >> >> 2014/1/9 Doug Hellmann : >>> >>> >>> >>> On Thu, Jan 9, 2014 at 1:53 PM, Nachi Ueno wrote: Hi folks Thank you for your input. The key difference from external configuration s

Re: [openstack-dev] [Neutron][3rd Party Testing]Remove voting until your testing structure works.

Hi Anita, et. all, I understand if the -1 is being voted because of testing framework failures, it is a real pain. Assuming the framework is working fine, I have noticed that there could be genuine failures because of devstack failing to fully stack up or the test failures. In my specific case, I

Re: [openstack-dev] [oslo.config] Centralized config management

On Thu, Jan 9, 2014 at 10:53 PM, Nachi Ueno wrote: > Hi folks > > Thank you for your input. > > The key difference from external configuration system (Chef, puppet > etc) is integration with > openstack services. > There are cases a process should know the config value in the other hosts. > If we

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

The UI will also need to be able to look at the Heat resources running within the overcloud stack and classify them according to a resource category. How do you envision that working? There's a way in a Heat template to specify arbitrary metadata on a resource. We can add flags in there and ke

Re: [openstack-dev] [oslo.config] Centralized config management

2014/1/9 Jeremy Hanmer : > Having run openstack clusters for ~2 years, I can't say that I've ever > desired such functionality. My proposal is adding functionalities, not removing it. so if you are satisfied with file based configuration with chef or puppet, this change won't affect you > How do

Re: [openstack-dev] [oslo.config] Centralized config management

On 01/09/2014 02:34 PM, Nachi Ueno wrote: > Hi Doug > > 2014/1/9 Doug Hellmann : >> >> >> >> On Thu, Jan 9, 2014 at 1:53 PM, Nachi Ueno wrote: >>> >>> Hi folks >>> >>> Thank you for your input. >>> >>> The key difference from external configuration system (Chef, puppet >>> etc) is integration wit

Re: [openstack-dev] Devstack on Fedora 20

That didn't seem to make a difference, still no cache. The RPMS are not getting installed, even if I deliberately add a line for python-dogpile-cache Shouldn't it get installed via pip without the rpm line? On 01/09/2014 02:27 PM, Sean Dague wrote: You need a working version of this patch

Re: [openstack-dev] [Solum][Pecan][Security] Pecan SecureController vs. Nova policy

Hi Adam, This looks very interesting. When do you expect to have this code available in oslo? Do you have a development guide which describes best practices for using this authorization approach? I think that for Pecan it will be possible to get rid of @protected wrapper and use SecureController

Re: [openstack-dev] [oslo.config] Centralized config management

Hi Doug Thank you for your input. 2014/1/9 Doug Hellmann : > > > > On Thu, Jan 9, 2014 at 2:34 PM, Nachi Ueno wrote: >> >> Hi Doug >> >> 2014/1/9 Doug Hellmann : >> > >> > >> > >> > On Thu, Jan 9, 2014 at 1:53 PM, Nachi Ueno wrote: >> >> >> >> Hi folks >> >> >> >> Thank you for your input. >> >

Re: [openstack-dev] [oslo.config] Centralized config management

Having run openstack clusters for ~2 years, I can't say that I've ever desired such functionality. How do you see these interactions defined? For instance, if I deploy a custom driver for Neutron, does that mean I also have to patch everything that will be talking to it (Nova, for instance) so th

Re: [openstack-dev] [oslo.config] Centralized config management

On Thu, Jan 9, 2014 at 2:34 PM, Nachi Ueno wrote: > Hi Doug > > 2014/1/9 Doug Hellmann : > > > > > > > > On Thu, Jan 9, 2014 at 1:53 PM, Nachi Ueno wrote: > >> > >> Hi folks > >> > >> Thank you for your input. > >> > >> The key difference from external configuration system (Chef, puppet > >> etc

Re: [openstack-dev] [Neutron][qa] Intermittent failure of tempest test test_network_basic_ops

Thanks Salvatore and Jay for sharing your experiences on this issue. I will look through the references you have provided to understand further as well. If I latch onto something, I will share back. BTW, before posting the question here, I did suspect some race conditions and tried to play aroun

Re: [openstack-dev] [oslo.config] Centralized config management

On Thu, Jan 9, 2014 at 7:53 PM, Nachi Ueno wrote: > One example of such case is neuron + nova vif parameter configuration > regarding to security group. > The workflow is something like this. > > nova asks vif configuration information for neutron server. > Neutron server ask configuration in neu

Re: [openstack-dev] [oslo.config] Centralized config management

Hi Doug 2014/1/9 Doug Hellmann : > > > > On Thu, Jan 9, 2014 at 1:53 PM, Nachi Ueno wrote: >> >> Hi folks >> >> Thank you for your input. >> >> The key difference from external configuration system (Chef, puppet >> etc) is integration with >> openstack services. >> There are cases a process shoul

Re: [openstack-dev] Devstack on Fedora 20

You need a working version of this patch to land - https://review.openstack.org/#/c/63647/ Because of the rhel6 support in devstack, every new version of fc needs manual support, because there are tons of packages needed in fc* that don't exist in rhel. -Sean On 01/09/2014 02:15 PM, Adam

Re: [openstack-dev] [oslo.config] Centralized config management

On Thu, Jan 9, 2014 at 1:53 PM, Nachi Ueno wrote: > Hi folks > > Thank you for your input. > > The key difference from external configuration system (Chef, puppet > etc) is integration with > openstack services. > There are cases a process should know the config value in the other hosts. > If we

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Ian, The idea of pci flavors is a great and using vendor_id and product_id make sense, but I could see a case for adding the class name such as 'VGA compatible controller'. Otherwise, slightly different generations of hardware will mean custom whitelist setups on each compute node. 01:00.0 V

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

Thanks! This is very informative. From a high-level perspective, this maps well with my understanding of how Tuskar will interact with various OpenStack services. A question or two inline: - Original Message - > I'm trying to hash out where data will live for Tuskar (both long term > an

[openstack-dev] Devstack on Fedora 20

So finally tried running a devstack instance on Fedora 20: rootwrap failed on the cinder stage of the install. So I scaled back to a Keystone only install. [fedora@ayoung-f20 devstack]$ cat localrc FORCE=yes ENABLED_SERVICES=key,mysql,qpid This failed starting the Keystone server with two

Re: [openstack-dev] [oslo.config] Centralized config management

Hi Jeremy Don't you think it is burden for operators if we should choose correct combination of config for multiple nodes even if we have chef and puppet? If we have some constraint or dependency in configurations, such logic should be in openstack source code. We can solve this issue if we have

Re: [openstack-dev] os-*-config in tripleo repositories

- Original Message - > From: "Derek Higgins" > To: "OpenStack Development Mailing List" > Sent: Thursday, January 9, 2014 8:13:53 AM > Subject: [openstack-dev] os-*-config in tripleo repositories > > It looks like we have some duplication and inconsistencies on the 3 > os-*-config elem

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

On Thu, 2014-01-09 at 07:46 -0500, Sean Dague wrote: > I think we are all agreed that the current state of Gate Resets isn't > good. Unfortunately some basic functionality is really not working > reliably, like being able to boot a guest to a point where you can ssh > into it. > > These are com

Re: [openstack-dev] [oslo.config] Centralized config management

Hi folks Thank you for your input. The key difference from external configuration system (Chef, puppet etc) is integration with openstack services. There are cases a process should know the config value in the other hosts. If we could have centralized config storage api, we can solve this issue.

Re: [openstack-dev] [nova] Bogus -1 scores from turbo hipster

- Original Message - > From: "Michael Still" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Tuesday, January 7, 2014 5:53:01 PM > Subject: Re: [openstack-dev] [nova] Bogus -1 scores from turbo hipster > > Hi. Thanks for reaching out about this. > > It

Re: [openstack-dev] [oslo.config] Centralized config management

+1 to Jay. Existing tools are both better suited to the job and work quite well in their current state. To address Nachi's first example, there's nothing preventing a Nova node in Chef from reading Neutron's configuration (either by using a (partial) search or storing the necessary information in

Re: [openstack-dev] [Neutron][qa] Intermittent failure of tempest test test_network_basic_ops

Hi Jay, replies inline. I have probably have found one more cause for this issue in the logs, and I have added a comment to the bug report. Salvatore On 9 January 2014 19:10, Jay Pipes wrote: > On Thu, 2014-01-09 at 09:09 +0100, Salvatore Orlando wrote: > > I am afraid I need to correct you J

Re: [openstack-dev] [oslo.config] Centralized config management

I agree with Doug’s question, but also would extend the train of thought to ask why not help to make Chef or Puppet better and cover the more OpenStack use-cases rather than add yet another competing system? Cheers, Morgan On January 9, 2014 at 10:24:06, Doug Hellmann (doug.hellm...@dreamhost.co

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

And my ring, my precious. Count me in! On 1/9/14, 6:06 AM, "Julien Danjou" wrote: >On Thu, Jan 09 2014, Sean Dague wrote: > >> I'm hopefully that if we can get everyone looking at this one a single >>day, >> we can start to dislodge the log jam that exists. > >I will help you bear this burd

Re: [openstack-dev] [oslo.config] Centralized config management

On Thu, 2014-01-09 at 10:23 +0100, Flavio Percoco wrote: > On 08/01/14 17:13 -0800, Nachi Ueno wrote: > >Hi folks > > > >OpenStack process tend to have many config options, and many hosts. > >It is a pain to manage this tons of config options. > >To centralize this management helps operation. > > >

Re: [openstack-dev] [oslo.config] Centralized config management

Nachi, Thanks for bringing this up. We've been thinking a lot about handling of configurations while working on Rubick. In my understanding, oslo.config could provide an interface to different back-ends to store configuration parameters. It could be simple centralized alternative to configuration

Re: [openstack-dev] [nova][documentation][devstack] Confused about how to set up a Nova development environment

Brant Knudson wrote on 01/09/2014 10:07:27 AM: > When I was starting out, I ran devstack ( http://devstack.org/ ) on > an Ubuntu VM. You wind up with a system where you've got a basic > running OpenStack so you can try things out with the command-line > utilities, and also do development becau

Re: [openstack-dev] [oslo.config] Centralized config management

What capabilities would this new service give us that existing, proven, configuration management tools like chef and puppet don't have? On Thu, Jan 9, 2014 at 12:52 PM, Nachi Ueno wrote: > Hi Flavio > > Thank you for your input. > I agree with you. oslo.config isn't right place to have server s

Re: [openstack-dev] [Savanna] Spark plugin status

This is definitely great news! +2 to the things Sergey mentioned below. Additionally, will you fill out the blueprint or wiki w/ details that will help others write integration tests for your plugin? And, did you integrate (or have plans to integrate) Spark into the EDP workflows in Horizon?

Re: [openstack-dev] [Neutron][qa] Intermittent failure of tempest test test_network_basic_ops

On Thu, 2014-01-09 at 09:09 +0100, Salvatore Orlando wrote: > I am afraid I need to correct you Jay! I always welcome corrections to things I've gotten wrong, so no worries at all! > This actually appears to be bug 1253896 [1] Ah, the infamous "SSH bug" :) Yeah, so last night I spent a few hours

Re: [openstack-dev] new (docs) requirement for third party CI

On Thu, Jan 9, 2014 at 5:52 AM, Kurt Taylor wrote: > Joe Gordon wrote on 01/08/2014 12:40:47 PM: > > > Re: [openstack-dev] [nova] new (docs) requirement for third party CI > > > > > > > On Jan 8, 2014 7:12 AM, "Matt Riedemann" > wrote: > > > > > > > If no one is against this or has something to

Re: [openstack-dev] [oslo.config] Centralized config management

Hi Flavio Thank you for your input. I agree with you. oslo.config isn't right place to have server side code. How about oslo.configserver ? For authentication, we can reuse keystone auth and oslo.rpc. Best Nachi 2014/1/9 Flavio Percoco : > On 08/01/14 17:13 -0800, Nachi Ueno wrote: >> >> Hi fo

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

I think I'm in agreement with all of this. Nice summary, Robert. It may not be where the work ends, but if we could get this done the rest is just refinement. On 9 January 2014 17:49, Robert Li (baoli) wrote: >Hi Folks, > > With John joining the IRC, so far, we had a couple of produc

[openstack-dev] [heat] python-heatclient installation failing on Windows

Hi Heat developers, On Windows platform (windows2012 and windows2008R2), I am seeing below given error when installing python-heatclient. Did any one see this problem earlier? c:\users\admin>pip -v install python-heatclient Downloading/unpacking python-heatclient Using version 0.2.6 (newest of

[openstack-dev] [TripleO][Tuskar] Domain Model Locations

I'm trying to hash out where data will live for Tuskar (both long term and for its Icehouse deliverables). Based on the expectations for Icehouse (a combination of the wireframes and what's in Tuskar client's api.py), we have the following concepts: = Nodes = A node is a baremetal machine on

Re: [openstack-dev] [Ceilometer] RFC: blueprint monitoring-network

Yuuichi, since you introduce switches that are currently not reflected in the Neutron entities, am I correct that a switch.port is always unknown to Neutron? Can a switch.port ever be a VM port? I'd be happy if you could help me understand this better. Best, Manuel

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi Folks, With John joining the IRC, so far, we had a couple of productive meetings in an effort to come to consensus and move forward. Thanks John for doing that, and I appreciate everyone's effort to make it to the daily meeting. Let's reconvene on Monday. But before that, and based on our t

Re: [openstack-dev] [savanna] savanna-ci usage

On 2014-01-09 14:16:09 +0400 (+0400), Sergey Lukjanov wrote: > we've finally updated our CI to use Zuul [...] Awesome! I can't wait to see your improvements. -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://list

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day - Mon Jan 27th

On Thu, Jan 9, 2014 at 11:30 PM, Sean Dague wrote: > Minor correction, we're going to do this on Jan 27th, to be after the i2 > push, as I don't think there is time organize this prior. > So FYI Jan 27th is a public holiday in Australia (Australia Day!), but given the timezone difference I think

Re: [openstack-dev] [nova][neutron] top gate bugs: a plea for help

I think I have found another fault triggering bug 1253896 when neutron is enabled. I've added a comment to https://bugs.launchpad.net/bugs/1253896 On another note, I'm seeing also occurrences of this bug with nova-network. Is there anybody from the nova side looking at it (I can give it a try, but

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day - Mon Jan 27th

Minor correction, we're going to do this on Jan 27th, to be after the i2 push, as I don't think there is time organize this prior. It will also be a good way to start the i3 push by trying to get the gate back in shape so that we can actually land what people need to land for i3. -Se

[openstack-dev] [all] bug for Jenkins slave agent init failures

Hi folks, sometimes Jenkins slaves failing due to the agent initialization error. There are several possible traces that you can see in such case: * Caused by: java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer (full stack trace: http://paste.openstac

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

On Jan 9, 2014, at 7:46 AM, Sean Dague wrote: > I think we are all agreed that the current state of Gate Resets isn't good. > Unfortunately some basic functionality is really not working reliably, like > being able to boot a guest to a point where you can ssh into it. > > These are common bug

Re: [openstack-dev] [OpenStack][HEAT][Dashboard] Edit JSON tempalte on OpenStack Dashboard

If so, can it be more functional, like syntax check and keyword check? -- David Xie Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Thursday, 9 January, 2014 at 17:41, Jay Lau wrote: > My bad, the image cannot be viewed. > > Upload again. > > Thanks, > > Jay > > > 2014/1/9 Jay L

Re: [openstack-dev] [nova][documentation][devstack] Confused about how to set up a Nova development environment

Mike - When I was starting out, I ran devstack ( http://devstack.org/ ) on an Ubuntu VM. You wind up with a system where you've got a basic running OpenStack so you can try things out with the command-line utilities, and also do development because it checks out all the repos. I learned a lot, and

Re: [openstack-dev] [Neutron] Allow multiple subnets on gateway port for router

-- (rebroadcast to dev community from prior unicast discussion) -- Hi Nir Sorry if the description is misleading. Didn't want a large title, and hoped that the description would provide those additional details to clarify the real goal of what's included and what's not included. #1. Yes, it's

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

Hi Sean, That is good idea, I also am in. BTW, what time will this work start? I tried to join this kind of work, but I could not find anyone on IRC in my timezone. Thanks Ken'ichi Ohmichi 2014/1/9 Sean Dague : > On 01/09/2014 08:01 AM, Thierry Carrez wrote: >> >> Sean Dague wrote: >>> >>> [..

Re: [openstack-dev] [Neutron] Allow multiple subnets on gateway port for router

-- (rebroadcast to dev community from prior unicast discussion) -- Hi Nir Sorry if the description is misleading. Didn't want a large title, and hoped that the description would provide those additional details to clarify the real goal of what's included and what's not included. #1. Yes, it's on

Re: [openstack-dev] os-*-config in tripleo repositories

Excerpts from Derek Higgins's message of 2014-01-09 06:13:53 -0700: > It looks like we have some duplication and inconsistencies on the 3 > os-*-config elements in the tripleo repositories > > os-apply-config (duplication) : >We have two elements that install this > diskimage-builder/elem

Re: [openstack-dev] [Nova] Icehouse mid-cycle meetup

On 11/25/2013 6:30 PM, Mike Wilson wrote: Hotel information has been posted. Look forward to seeing you all in February :-). -Mike On Mon, Nov 25, 2013 at 8:14 AM, Russell Bryant mailto:rbry...@redhat.com>> wrote: Greetings, Other groups have started doing mid-cycle meetups with su

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

On Thu, Jan 9, 2014 at 1:46 PM, Sean Dague wrote: > Specifically I'd like to get commitments from as many PTLs as possible > that they'll both directly participate in the day, as well as encourage the > rest of their project to do the same > I'll be more than happy to participate (or at least on

Re: [openstack-dev] [Openstack][Nova][Docker] Devstack with docker driver

Hi Daniel, I think it was some proxy issue prohibiting from the download. I downloaded the correct docker-registry.tar.gz and stack.sh completed but with some issues remain related to image availability. The docker push is getting *"HTTP code 500 while uploading metadata: invalid character '<' loo

Re: [openstack-dev] os-*-config in tripleo repositories

On 09/01/14 14:13, Derek Higgins wrote: It looks like we have some duplication and inconsistencies on the 3 os-*-config elements in the tripleo repositories os-apply-config (duplication) : We have two elements that install this diskimage-builder/elements/config-applier/ tripleo-i

Re: [openstack-dev] [heat] Sofware Config progress

On 01/08/2014 06:57 PM, Prasad Vellanki wrote: Clint & Steve One scenario we are trying to see is whether and how Heat software-config enables deployment of images available from third party as virtual appliances, providing network, security or acceleration capabilities. The vendor in some

  1   2   >