Re: [openstack-dev] [neutron] explanations on the current state of config file handling

On 05/03/2014 12:48 AM, Mark T. Voelker wrote: > I think it's not just devstack/grenade that would benefit from this. > Variance in the plugin configuration patterns is a fairly common > complaint I hear from folks deploying OpenStack, and going to a single > config would likely make that easier.

Re: [openstack-dev] [qa] QA Summit Meet-up Atlanta

All right, let’s meet on Monday ;) We can discuss the details after the QA meeting this week. Von: Frittoli, Andrea (HP Cloud) [mailto:fritt...@hp.com] Gesendet: Donnerstag, 1. Mai 2014 18:42 An: OpenStack Development Mailing List (not for usage questions) Betreff: Re: [openstack-dev] [qa] QA Summ

[openstack-dev] [Openstack-dev][qa] Running tempest tests against existing openstack installation

Hello, I am trying to run tempest tests against an existing openstack deployment. I have configured tempest.conf for the environment details. But when I execute run_tempest.sh, it does not run any tests. Although when I run testr run, the tests fail with *NoSuchOptError: no such option: IMAGE_ID*

Re: [openstack-dev] [Nova][Heat] Custom Nova Flavor creation through Heat (pt.2)

>Having project-scoped flavors will rid us of the identified issues, and will allow a more fine-grained way of managing physical resources. Flavors concept was introduced in clouds to solve issue with effective physical resource usage: 8Gb physical memory can be effectively splitted to two m2.my_s

[openstack-dev] [infra] Meeting Tuesday May 6th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is hosting our weekly meeting on Tuesday May 6th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interested in i

Re: [openstack-dev] [qa] [cinder] Do we now require schema response validation in tempest clients?

On Thu, May 1, 2014 at 1:32 PM, Ken'ichi Ohmichi wrote: > Hi David, > > 2014-05-01 5:44 GMT+09:00 David Kranz : > > There have been a lot of patches that add the validation of response > dicts. > > We need a policy on whether this is required or not. For example, this > patch > > > > https://revie

[openstack-dev] [nova] Do we have a way to add a non-nova managed host to nova managed?

Hi Not sure ti's proper to ask this question here, or maybe someone asked this question before and discussion , please share info to me if we have If we have a bunch of hosts that used to manage by them self, some vm and hypervisors already running on the hosts

[openstack-dev] [nova] Question about addit log in nova-compute.log

Hi I saw in my compute.log has following logs which looks to me strange at first, Free resource is negative make me confused and I take a look at the existing code looks to me the logic is correct and calculation doesn't have problem ,but the output 'Free' is confusin

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

External networks can be handled just like regular networks by not specifying the external bridge. They will then be tagged with the provider network information just like any other tenant network. On Sun, May 4, 2014 at 6:52 PM, gustavo panizzo wrote: > On 05/04/2014 01:22 PM, Mark McClain wro

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

On 05/04/2014 01:22 PM, Mark McClain wrote: > > >> On May 4, 2014, at 8:08, "Sean Dague" wrote: >> >> Question (because I honestly don't know), when would you want more than >> 1 l3 agent running on the same box? > > For the legacy case where there are multiple external networks connected to a

Re: [openstack-dev] [ML2] L2 population mechanism driver

Hi Slawek, I think L2 pop driver needs to be used in conjunction with other mechanism drivers. It only deals with pro-actively informing agents on which MAC Addresses became available/unavailable on cloud nodes and is not meant for binding/unbinding ports on segments. If you configure mechanis

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

I second the conf.d model. Regards, Mandeep On Sun, May 4, 2014 at 10:13 AM, John Dickinson wrote: > To add some color, Swift supports both single conf files and conf.d > directory-based configs. See > http://docs.openstack.org/developer/swift/deployment_guide.html#general-service-configuratio

Re: [openstack-dev] Monitoring as a Service

One of the advantages of the program concept within OpenStack is that separate code projects with complementary goals can be managed under the same program without needing to be the same codebase. The most obvious example across every program are the "server" and "client" projects under most pro

[openstack-dev] [ML2] L2 population mechanism driver

Hello, Last time I want to try using L2pop mechanism driver in ML2 (and openvswitch agents on compute nodes). But every time when I try to spawn instance I have got error "binding failed". After some searching in code I found that l2pop driver have not implemented method "bind_port" and as it i

Re: [openstack-dev] Monitoring as a Service

Hello to All. I also +1 this idea. As I can see, Telemetry program (according to Launchpad) covers the process of the infrastructure metrics (networking, etc) and in-compute-instances metrics/monitoring. So, the best option, I guess, is to propose add such great feature to Ceilometer. In-compute-i

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

To add some color, Swift supports both single conf files and conf.d directory-based configs. See http://docs.openstack.org/developer/swift/deployment_guide.html#general-service-configuration. The "single config file" pattern is quite useful for simpler configurations, but the directory-based on

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

If the consensus is to unify all the config options into a single configuration file, I'd suggest following what the Nova folks did with [1], which I think is what Salvatore was also hinted. This will also help mitigate needless source code conflicts that would inevitably arise when merging competi

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

> On May 4, 2014, at 8:08, "Sean Dague" wrote: > > Question (because I honestly don't know), when would you want more than > 1 l3 agent running on the same box? For the legacy case where there are multiple external networks connected to a node on different bridges. ___

Re: [openstack-dev] Monitoring as a Service

On Sun, May 4, 2014 at 9:37 AM, Thomas Goirand wrote: > On 05/02/2014 05:17 AM, Alexandre Viau wrote: > > Hello Everyone! > > > > My name is Alexandre Viau from Savoir-Faire Linux. > > > > We have submited a Monitoring as a Service blueprint and need feedback. > > > > Problem to solve: Ceilometer

Re: [openstack-dev] Monitoring as a Service

On 05/02/2014 05:17 AM, Alexandre Viau wrote: > Hello Everyone! > > My name is Alexandre Viau from Savoir-Faire Linux. > > We have submited a Monitoring as a Service blueprint and need feedback. > > Problem to solve: Ceilometer's purpose is to track and *measure/meter* usage > information colle

Re: [openstack-dev] [nova] Proposal: remove the server groups feature

The topic is "Scheduler hints for VM life cycle". Thanks. 2014-05-04 10:06 GMT+08:00 Qiming Teng : > On Thu, May 01, 2014 at 08:49:11PM +0800, Jay Lau wrote: > > Jay Pipes and all, I'm planning to merge this topic to > >

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

On 05/03/2014 03:53 PM, gustavo panizzo wrote: > On 05/02/2014 11:09 AM, Mark McClain wrote: >> >> To throw something out, what if moved to using config-dir for optional >> configs since it would still support plugin scoped configuration files. >> >> Neutron Servers/Network Nodes >> /etc/neutro

Re: [openstack-dev] nova compute error

Hi I changed the ebtables version i.e ebtables_2.0.9.2-2ubuntu3_powerpc.deb from version 2.0.10-4 and the error just reduced to one as below... 2014-05-03 11:26:42.052 12065 TRACE nova.openstack.common.rpc.amqp if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)

[openstack-dev] [Cinder] Confusion about the respective use cases for volume's admin_metadata, metadata and glance_image_metadata

Hi, stackers: I have some confusion about the respective use cases for volume's admin_metadata, metadata and glance_image_metadata. I know glance_image_metadata comes from image which is the volume created from, and it is immutable. Glance_image_metadata is used for many cases, such as billin