Re: [openstack-dev] How to get VXLAN Endpoint IP without agent

Though we can configure in Nova.conf file, but we have to make sure these tunnel interface ipaddress of every compute node and nova.conf will have the same configuration. But it is still painful to make sure that the ipaddress are configured properly. We want to come up with BP to avoid these ma

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/22/2013 02:12 AM, Jeremy Stanley wrote: > On 2013-10-22 01:45:13 +0800 (+0800), Thomas Goirand wrote: > [...] >> The main problem I was facing was that troveclient has a few files >> stating that HP was the sole copyright holder, when it clearly was >> not (since I have discussed a bit with s

Re: [openstack-dev] Gerrit tools

On 21/10/13 15:55 +, Joshua Harlow wrote: I am using gerritlib in the curses ui; seems to work nicely. Only 1 thing that I don't like so much is that it silences connection/other errors from what I can tell. See _run() method in https://github.com/openstack-infra/gerritlib/blob/master/ger

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/22/2013 04:45 AM, Mark McLoughlin wrote: > By "improve clarity", you mean "compile an accurate list of all > copyright holders"? Why is this useful information? > > Sure, we could also "improve clarity" by compiling a list of all the > cities in the world where some OpenStack code has been a

Re: [openstack-dev] Gerrit tools

On 21/10/13 15:41 +0200, Chmouel Boudjnah wrote: On Mon, Oct 21, 2013 at 3:03 PM, Flavio Percoco wrote: Also realize that OpenStack maintains gerritlib - https://github.com/ openstack-infra/gerritlib Which anyone can contribute to (and is the code that every message

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/22/2013 08:09 AM, Monty Taylor wrote: > b) Thomas should put in debian/copyright what is in our headers, and > should consider them, as they are in our source tarballs, to be correct > c) If Thomas, or anyone else, considers our header attribution to be > incorrect, he or she should submit a

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Tue, 2013-10-22 at 14:09 +0800, Thomas Goirand wrote: > On 10/22/2013 04:55 AM, Mark McLoughlin wrote: > > Talk to the Trove developers and politely ask them whether the copyright > > notices in their code reflects what they see as the reality. > > > > I'm sure it would help them if you pointed

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/22/2013 04:48 AM, Mark McLoughlin wrote: > On Tue, 2013-10-22 at 01:55 +0800, Thomas Goirand wrote: >> On 10/21/2013 09:28 PM, Mark McLoughlin wrote: >>> In other words, what exactly is a list of copyright holders good for? >> >> At least avoid pain and reject when uploading to the Debian NEW

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/22/2013 05:06 AM, Michael Basnight wrote: > so if this is sufficient, ill fix the copyright headers. Please do (and backport that to 2013.2...)! :) Thomas ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.or

Re: [openstack-dev] [Neutron] Common requirements for services' discussion

Hi All, This is a reminder for the next IRC meeting on Tuesday (Oct 22nd) 15.30 UTC (8.30 AM PDT) on the #openstack-meeting-alt channel. The proposed agenda is: * Service insertion and chaining * Service agents * Service VMs - mechanism * Service VMs - policy * Extensible APIs for services and an

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/22/2013 04:55 AM, Mark McLoughlin wrote: > Talk to the Trove developers and politely ask them whether the copyright > notices in their code reflects what they see as the reality. > > I'm sure it would help them if you pointed out to them some significant > chunks of code from the commit hist

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Tue, 2013-10-22 at 01:09 +0100, Monty Taylor wrote: > The last thing we need to do is validate in any manner that somehow the > CLA makes our Apache Licensed Free Software more Free or more Valid than > if we did not have our useless CLA. Agree with this. My simplified way of thinking about th

[openstack-dev] [Mistral] Teem meeting minutes - 10/21

I'd like to thank everyone who joined our meeting and who generally got interested in the project. Here's the log and meeting minutes: Log: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-10-21-16.00.log.html Minutes: http://eavesdrop.openstack.org/meetings/mis

Re: [openstack-dev] question regarding vmdk file format for baremetal provisioning

The vmdk i have is from a VM that has not been partitioned, does it mean, it will not work? Meaning, i cannot use an off the shelf kernel, ramdisk and use the qcow2-converted-image-from-vmdk? Thanks Ravi On Mon, Oct 21, 2013 at 8:18 PM, Robert Collins wrote: > You'll need a format qemu-img supp

Re: [openstack-dev] question regarding disk image builder

Thanks, Rob. On the console, I see cloud-init starting up and it prints something like this ci-info lo0 : 127.0.0.1 255.0.0.0 ci-info eth0 : - - ci-info eth1 : - - Soon afterwards, I see this message repeat for 120s util.py [WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/insta

Re: [openstack-dev] question regarding vmdk file format for baremetal provisioning

You'll need a format qemu-img supports; diskimage-builder outputs qcow2 by default, for instance. Also note it must be a partition image, not a full disk image. Cheers, Rob On 22 October 2013 16:15, Ravikanth Samprathi wrote: > Hi > Am using a vmdk file for provisioning baremetal. But the nova

Re: [openstack-dev] question regarding disk image builder

You need to disable file injection in nova, and you need to have link up on the interfaces, or dhcp-all-interfaces will skip them. What do you see in the node console specifically? -Rob On 22 October 2013 16:11, Ravikanth Samprathi wrote: > Hi Folks > > I'm using DiB to create an ubuntu 12.04 i

[openstack-dev] question regarding vmdk file format for baremetal provisioning

Hi Am using a vmdk file for provisioning baremetal. But the nova failed with nova-compute log having the following message: ERROR nova.compute.manager . Unexpected error while running command qemu-img convert error while reading sector 131072 Invalid argument. Can someone provide some

[openstack-dev] question regarding disk image builder

Hi Folks I'm using DiB to create an ubuntu 12.04 image where dhcp is enabled on all interfaces, and .ssh/authorized_keys is copied $ bin/disk-image-create -a amd64 -o u1204.am d64.custom ubuntu local-config dhcp-all-interfaces I see DiB printing these messages indicating it worked as expecte

[openstack-dev] [Heat] Incorporate Auditing Support / Usage Notifications

Hi all There has been some interest in Heat generating usage notifications http://summit.openstack.org/cfp/details/87 so I thought I'd implement the blueprint: https://blueprints.launchpad.net/heat/+spec/send-notification I'd like to ask for suggestions on the content of the notifications. I ha

Re: [openstack-dev] [Nova] What validation feature is necessary for Nova v3 API

Hi Doug, Thanks again. -Original Message- From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com] Sent: Tuesday, October 22, 2013 6:51 AM To: Ohmichi, Kenichi Cc: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Nova] What validation feature is necessary for Nova v3 AP

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Oct 21, 2013, at 5:09 PM, Monty Taylor wrote: > On 10/21/2013 10:44 PM, Clint Byrum wrote: >> Excerpts from Mark McLoughlin's message of 2013-10-21 13:45:21 -0700: >>> On Mon, 2013-10-21 at 10:28 -0700, Clint Byrum wrote: Excerpts from Robert Collins's message of 2013-10-20 02:25:43 -0700:

Re: [openstack-dev] [Nova] VMWare Mine Sweeper, Congrats!

Yes - we are going to change that. I know it's annoying. Sent from my iPhone > On Oct 21, 2013, at 5:14 PM, Michael Still wrote: > > This is super cool. Thanks! > > One piece of feedback -- would it be possible to get the results as > something other than a tarball? Downloading the entire t

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/21/2013 10:44 PM, Clint Byrum wrote: > Excerpts from Mark McLoughlin's message of 2013-10-21 13:45:21 -0700: >> On Mon, 2013-10-21 at 10:28 -0700, Clint Byrum wrote: >>> Excerpts from Robert Collins's message of 2013-10-20 02:25:43 -0700: On 20 October 2013 02:35, Monty Taylor wrote:

Re: [openstack-dev] [Nova] VMWare Mine Sweeper, Congrats!

This is super cool. Thanks! One piece of feedback -- would it be possible to get the results as something other than a tarball? Downloading the entire tarball to read one log is slightly annoying. Thanks, Michael On Sat, Oct 19, 2013 at 9:29 AM, Sreeram Yerrapragada wrote: > We had some infrast

[openstack-dev] [infra] Meeting Tuesday October 22nd at 19:00 UTC

The OpenStack Infrastructure (Infra) team is hosting our weekly meeting tomorrow, Tuesday October 22nd, 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 inf

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

On Mon, Oct 21, 2013 at 2:04 PM, Michael Basnight wrote: > > On Oct 21, 2013, at 1:40 PM, Tim Simpson wrote: > > >>> 2. I also think a datastore_version alone should be sufficient since > the associated datastore type will be implied: > > > >> When i brought this up it was generally discussed as b

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects

On 2013-10-21 14:44:10 -0700 (-0700), Clint Byrum wrote: [...] > I assume the other CLA's have the same basic type of license being > granted to the OpenStack Foundation. [...] For the record, there are only two other CLAs in place for OpenStack source code contributions. One is the Corporate CLA

Re: [openstack-dev] [Nova] What validation feature is necessary for Nova v3 API

On Mon, Oct 21, 2013 at 7:14 AM, Kenichi Oomichi wrote: > > Hi Doug, > > Thank you for your advice. > > Some validation features seem necessary as basic features for Nova APIs. > so I am trying to pick necessary features for WSME on the following > inline messages. > > Could you check them? > > >

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

Excerpts from Mark McLoughlin's message of 2013-10-21 13:45:21 -0700: > On Mon, 2013-10-21 at 10:28 -0700, Clint Byrum wrote: > > Excerpts from Robert Collins's message of 2013-10-20 02:25:43 -0700: > > > On 20 October 2013 02:35, Monty Taylor wrote: > > > > > > > However, even as a strong suppor

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

On Mon, Oct 21, 2013 at 11:40 PM, Tim Simpson wrote: > > >> 4. Additionally, in the current pull request to implement this it is > >> possible to avoid passing a version, but only if no more than one version > >> of the datastore_type exists in the database. > >> > >> I think instead the datasto

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

On Oct 21, 2013, at 1:57 PM, Nikhil Manchanda wrote: > > The image approach works fine if Trove only supports deploying a single > datastore type (mysql in your case). As soon as we support > deploying more than 1 datastore type, Trove needs to have some knowledge > of which guestagent manager c

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Oct 21, 2013, at 1:55 PM, Mark McLoughlin wrote: > On Tue, 2013-10-22 at 01:45 +0800, Thomas Goirand wrote: >> On 10/20/2013 09:00 PM, Jeremy Stanley wrote: >>> On 2013-10-20 22:20:25 +1300 (+1300), Robert Collins wrote: >>> [...] OTOH registering one's nominated copyright holder on the f

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

On Oct 21, 2013, at 1:40 PM, Tim Simpson wrote: >>> 2. I also think a datastore_version alone should be sufficient since the >>> associated datastore type will be implied: > >> When i brought this up it was generally discussed as being confusing. Id >> like to use type and rely on having a def

Re: [openstack-dev] [Heat] HOT Software configuration proposal

On 10/22/2013 08:45 AM, Mike Spreitzer wrote: > Steve Baker wrote on 10/15/2013 06:48:53 PM: > > > I've just written some proposals to address Heat's HOT software > > configuration needs, and I'd like to use this thread to get some > feedback: > > https://wiki.openstack.org/wiki/Heat/Blueprints/ho

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

The image approach works fine if Trove only supports deploying a single datastore type (mysql in your case). As soon as we support deploying more than 1 datastore type, Trove needs to have some knowledge of which guestagent manager classes to load. Hence the need for having a datastore type API.

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Tue, 2013-10-22 at 01:45 +0800, Thomas Goirand wrote: > On 10/20/2013 09:00 PM, Jeremy Stanley wrote: > > On 2013-10-20 22:20:25 +1300 (+1300), Robert Collins wrote: > > [...] > >> OTOH registering one's nominated copyright holder on the first > >> patch to a repository is probably a sustainable

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Tue, 2013-10-22 at 01:55 +0800, Thomas Goirand wrote: > On 10/21/2013 09:28 PM, Mark McLoughlin wrote: > > In other words, what exactly is a list of copyright holders good for? > > At least avoid pain and reject when uploading to the Debian NEW queue... I'm sorry, that is downstream Debian pai

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Mon, 2013-10-21 at 10:28 -0700, Clint Byrum wrote: > Excerpts from Robert Collins's message of 2013-10-20 02:25:43 -0700: > > On 20 October 2013 02:35, Monty Taylor wrote: > > > > > However, even as a strong supporter of accurate license headers, I would > > > like to know more about the FTP m

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

>> 2. I also think a datastore_version alone should be sufficient since the >> associated datastore type will be implied: >When i brought this up it was generally discussed as being confusing. Id like >to use type and rely on having a default (or active) version behind the scenes. Can't we do b

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

What is the major motivation not to simply use a glance image named "MySQL 5.5" or "MongoDB 2.4"? Wouldn't that give service providers all the flexibility they need for providing different types? For example, I could offer a simple "MySQL" image that creates a MySQL instance. If all my users use t

Re: [openstack-dev] [Heat] HOT Software configuration proposal

On 21/10/13 15:45 -0400, Mike Spreitzer wrote: Steve Baker wrote on 10/15/2013 06:48:53 PM: I've just written some proposals to address Heat's HOT software configuration needs, and I'd like to use this thread to get some feedback: https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-

Re: [openstack-dev] [Trove] Testing of new service types support

Michael, Tim, Nice to see you, guys, agreed. But what should I do now? Dive into trove-integration? I guess there will be no use of mocked tests, coz I haven't actually written a single line of server side code. All the fun is in guest agent. Thanks >> For the api stuff, sure thats fine. i just

[openstack-dev] [marconi] Minutes from today's meeting

Folks, Today the Marconi team held their regularly scheduled meeting in #openstack-meeting-alt @ 1600 UTC. We discussed progress on the new storage sharding feature which will let Marconi scale to very large deployments, and provide a solid foundation for implementing queue "flavors" depending

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

On Oct 18, 2013, at 12:30 PM, Tim Simpson wrote: > 1. I think since we have two fields in the instance object we should make a > new object for datastore and avoid the name prefixing, like this: I agree with this. > 2. I also think a datastore_version alone should be sufficient since the > as

Re: [openstack-dev] Havana neutron security groups config issue

We tried that a few minutes ago, and removing nova-networks doesnt make any difference, im starting to think that neutron security groups are not working with dockerIO containers On Mon, Oct 21, 2013 at 4:15 PM, Aaron Rosen wrote: > Hrm, your config files looks good to me. From your iptables-sa

Re: [openstack-dev] [Heat] HOT Software configuration proposal

Steve Baker wrote on 10/15/2013 06:48:53 PM: > I've just written some proposals to address Heat's HOT software > configuration needs, and I'd like to use this thread to get some feedback: > https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config > https://wiki.openstack.org/wiki/He

Re: [openstack-dev] [Trove] Testing of new service types support

>> For the api stuff, sure thats fine. i just think the overall coverage of the >> review will be quite low if we are only testing the API via fake code. We're in agreement here, I think. I will say though that if the people working on Mongo want to test it early, and go beyond simply using the

Re: [openstack-dev] Havana neutron security groups config issue

Hrm, your config files looks good to me. From your iptables-save output it looks like you have nova-network running as well. I wonder if that is overwritting the rules that the agents are installing. Can you try removing nova-network and see if that changes anything? Aaron On Mon, Oct 21, 2013 a

Re: [openstack-dev] [TripleO] Tuskar UI - Resource Class Creation Wireframes - updated

Hi Jarda, Below you will find my comments and questions on the latest version of the Resource Class Creation wireframes. Please let me know if you have any questions. Thanks, Liz On Oct 16, 2013, at 12:31 PM, Jaromir Coufal wrote: > Hey folks, > > I am sending an updated version of wireframe

Re: [openstack-dev] Distributed Virtual Router Discussion

Hi Swaminathan. I work for a virtual networking startup called Midokura and I'm very interested in joining the discussion. We currently have distributed router implementation using existing Neutron API. Could you clarify why distributed vs centrally located routing implementation need to be dis

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 2013-10-22 01:45:13 +0800 (+0800), Thomas Goirand wrote: [...] > The main problem I was facing was that troveclient has a few files > stating that HP was the sole copyright holder, when it clearly was > not (since I have discussed a bit with some the dev team in > Portland, IIRC some of them are

Re: [openstack-dev] Towards OpenStack Disaster Recovery

From: Caitlin Bestler To: openstack-dev@lists.openstack.org, Date: 21/10/2013 06:55 PM Subject:Re: [openstack-dev] Towards OpenStack Disaster Recovery >> >> Hi all, >> We (IBM and Red Hat) have begun discussions on enabling Disaster Recovery >> (DR) in OpenStack. >> >> We have cre

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/21/2013 09:28 PM, Mark McLoughlin wrote: > In other words, what exactly is a list of copyright holders good for? At least avoid pain and reject when uploading to the Debian NEW queue... Thomas Goirand (zigo) ___ OpenStack-dev mailing list OpenSt

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/20/2013 09:38 PM, Jeremy Stanley wrote: > Part of the issue is that historically the project has held a > laissez faire position that claiming copyright on contributions is > voluntary, and that if you don't feel your modifications to a > particular file are worthy of copyright (due to trivia

[openstack-dev] [Neutron] IPv6 & DHCP options for dnsmasq

Hi, Looking at the code for the linux DHCP agent, there's a comment about trying to figure out how to indicate other options (ra-only, slaac, ra-nameservers, and ra-stateless). https://github.com/openstack/neutron/blob/master/neutron/agent/linux/dhcp.py#L330 I decided to take a crack at creating

[openstack-dev] Disable async network allocation

Hi Folks, I'm trying to track down a couple of obsecure issues in network port creation where it would be really useful if I could disable the async network allocation so that everything happens in the context of a single eventlet rather than two (and also rule out if there is some obscure even

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/20/2013 09:00 PM, Jeremy Stanley wrote: > On 2013-10-20 22:20:25 +1300 (+1300), Robert Collins wrote: > [...] >> OTOH registering one's nominated copyright holder on the first >> patch to a repository is probably a sustainable overhead. And it's >> probably amenable to automation - a commit h

Re: [openstack-dev] Havana neutron security groups config issue

Aaron, Here you are all the info, all the nova.confs (compute, controller) , all the agent logs, iptables output etc ... btw as i said we're testing this setup with docker containers , just to be clear regarding your last recommedation about libvirt vif driver (that we alreade have on the conf )

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

Excerpts from Robert Collins's message of 2013-10-20 02:25:43 -0700: > On 20 October 2013 02:35, Monty Taylor wrote: > > > However, even as a strong supporter of accurate license headers, I would > > like to know more about the FTP masters issue. I dialog with them, as > > folks who deal with thi

Re: [openstack-dev] [Trove] Testing of new service types support

On Oct 21, 2013, at 10:02 AM, Tim Simpson wrote: > Can't we say that about nearly any feature though? In theory we could put a > hold on any tests for feature work saying it > will need to be redone when Tempest integrated is finished. > > Keep in mind what I'm suggesting here is a fairly triv

Re: [openstack-dev] Towards OpenStack Disaster Recovery

Hi Caitlin, Caitlin Bestler wrote on 21/10/2013 06:51:36 PM: > On 10/21/2013 2:34 AM, Avishay Traeger wrote: > > > > Hi all, > > We (IBM and Red Hat) have begun discussions on enabling Disaster Recovery > > (DR) in OpenStack. > > > > We have created a wiki page with our initial thoughts: > > ht

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

It is not just the development effort but also those users who rely on tempest to probe their production environments. If there is a second project, they'd have to configure the endpoints, user accounts etc. in both systems. In my view, this cannot be done at the gate, it would take too long bu

Re: [openstack-dev] [Trove] Testing of new service types support

Can't we say that about nearly any feature though? In theory we could put a hold on any tests for feature work saying it will need to be redone when Tempest integrated is finished. Keep in mind what I'm suggesting here is a fairly trivial change to get some validation via the existing fake mode

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/20/2013 06:00 AM, Jeremy Stanley wrote: > I know the Foundation's got work underway to improve the affiliate > map from the member database, so it might be possible to have some > sort of automated job which proposes changes to a copyright holders > list in each project by running a query wit

Re: [openstack-dev] [Trove] Testing of new service types support

Top posting… Id like to see these in the tempest tests. Im just getting started integrating trove into tempest for testing, and there are some prerequisites that im working thru with the infra team. Progress is being made though. Id rather not see them go into 2 different test suites if we can

Re: [openstack-dev] [Heat] Plugin to use Docker containers a resources in a template

On 10/17/2013 09:06 PM, Sam Alba wrote: > Hi all, > > I've been recently working on a Docker plugin for Heat that makes it > possible to use Docker containers as resources. > > I've just opened the repository: > https://github.com/dotcloud/openstack-heat-docker Related to this discussion, we'll

Re: [openstack-dev] Gerrit tools

The nice thing about the current ssh is that it is doing "push" notifications over ssh, if the rest API supported that it would be great; instead of a pull notification via rest. Sent from my really tiny device... On Oct 21, 2013, at 6:48 AM, "Chmouel Boudjnah" mailto:chmo...@enovance.com>> wr

Re: [openstack-dev] [Trove] Testing of new service types support

Hi Tim, Thanks for a quick reply. I'll go with updating run_tests.py for now. Hope, Andrey Shestakov's changes arrive soon. Best wishes. On Mon, Oct 21, 2013 at 7:01 PM, Tim Simpson wrote: > Hi Illia, > > You're correct; until the work on establishing datastore types and > versions as a fir

[openstack-dev] Distributed Virtual Router Discussion

Hi Folks, I am currently working on a blueprint for Distributed Virtual Router. If anyone interested in being part of the discussion please let me know. I have put together a first draft of my blueprint and have posted it on Launchpad for review. https://blueprints.launchpad.net/neutron/+spec/neut

[openstack-dev] [Murano] Team Meeting minutes - 10/21

Hi, Thanks everyone who has joined Murano IRC meeting. These are the meeting minutes and the action items: http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-10-21-15.00.html Complete logs can be found here: http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-10-21-15.00.l

Re: [openstack-dev] [Trove] Testing of new service types support

Hi Illia, You're correct; until the work on establishing datastore types and versions as a first class Trove concept is finished, which will hopefully be soon (see Andrey Shestakov's pull request), testing non-MySQL datastore types will be problematic. A short term, fake-mode only solution cou

Re: [openstack-dev] Gerrit tools

Neat didn't know about this library :) Thx for the +1! Sent from my really tiny device... > On Oct 21, 2013, at 1:08 AM, "Flavio Percoco" wrote: > >> On 20/10/13 05:01 +, Joshua Harlow wrote: >> I created some gerrit tools that I think others might find useful. >> >> https://github.com/ha

Re: [openstack-dev] Gerrit tools

I am using gerritlib in the curses ui; seems to work nicely. Only 1 thing that I don't like so much is that it silences connection/other errors from what I can tell. See _run() method in https://github.com/openstack-infra/gerritlib/blob/master/gerritlib/gerrit.py Otherwise pretty easy to use.

Re: [openstack-dev] Towards OpenStack Disaster Recovery

On 10/21/2013 2:34 AM, Avishay Traeger wrote: Hi all, We (IBM and Red Hat) have begun discussions on enabling Disaster Recovery (DR) in OpenStack. We have created a wiki page with our initial thoughts: https://wiki.openstack.org/wiki/DisasterRecovery We encourage others to contribute to this wi

Re: [openstack-dev] [Heat] A prototype for cross-vm synchronization and communication

On Fri, Oct 18, 2013 at 02:45:01PM -0400, Lakshminaraya Renganarayana wrote: > The prototype is implemented in Python and Ruby is used for chef > interception. Where can we find the code? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [Nova] support for multiple active scheduler policies/drivers

I'm not sure it's a good moment for this but I would like to re-open the topic a little bit. Just a small idea: is it OK if we use a file, or a database as a central point to store the policies and their associated aggregates? The Scheduler reads it first, then calls the scheduler drivers lis

Re: [openstack-dev] [Heat] HOT Software orchestration proposal for workflows

On 18/10/13 20:24, John Davidge -X (jodavidg - AAP3 INC at Cisco) wrote: It looks like this discussion involves many of the issues faced when developing the Curvature & Donabe frameworks, which were presented at the Portland Summit - slides and video here: http://www.openstack.org/summit/portlan

Re: [openstack-dev] [Heat] Plugin to use Docker containers a resources in a template

On 18/10/13 03:06, Sam Alba wrote: Hi all, I've been recently working on a Docker plugin for Heat that makes it possible to use Docker containers as resources. I've just opened the repository: https://github.com/dotcloud/openstack-heat-docker Cool, nice work. Thanks for sharing! :) I agree t

Re: [openstack-dev] [Heat] A prototype for cross-vm synchronization and communication

Thomas Spatzier wrote on 10/21/2013 08:29:47 AM: > you mentioned an example in your original post, but I did not find it. Can > you add the example? Hi Thomas, Here is the example I used earlier: For example, consider a two VM app, with VMs vmA, vmB, and a set of software components (ai's and

Re: [openstack-dev] [Heat] A prototype for cross-vm synchronization and communication

Hi Stan, Thanks for the comments. As you have observed the prototype that I have built is tied to Chef. I just wanted to describe that here for reference and not as a proposal for the general implementation. What I would like to work on is a more general solution that is agnostic to (or works wi

[openstack-dev] [Trove] Testing of new service types support

Hi all, I've done with implementing the very first bits of MongoDB support in Trove along with unit tests and faced an issue with proper testing of it. It is well known that right now only one service type per installation is supported by Trove (it is set in config). All testing infrastructure, i

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

2. it can be confusing coz not clear to what type version belongs (possible add "type" field in version). also if you have default type, then specified version recognizes as version of default type (no lookup in version.datastore_type_id) but i think we can do lookup in version.datastore_type_id

Re: [openstack-dev] [ceilometer] [qa] Ceilometer ERRORS in normal runs

Sean, we currently have a BP out there to investigate basic tempest integration and I think this might fall under the same umbrella. Unfortunately I've not been able to free up my development time for it, but I've assigned it out to someone who can take a look and report back. https://blueprint

Re: [openstack-dev] [qa][keystone] Adding client library related tests to tempest

On Mon, Oct 21, 2013 at 08:14:03AM -0400, Sean Dague wrote: > On 10/21/2013 05:19 AM, Steven Hardy wrote: > > >> > >>Definitely agree we should have plenty of end-to-end tests in the > >>gate, it's the reason we've got the scenario tests, to do exactly > >>this kind of through testing. > > > >Ok,

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

On 10/20/2013 02:36 PM, Alex Gaynor wrote: There's several issues involved in doing automated regression checking for benchmarks: - You need a platform which is stable. Right now all our CI runs on virtualized instances, and I don't think there's any particular guarantee it'll be the same underl

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

Thanks for the feedback Andrey. >> 2. Got this case in irc, and decided to pass type and version together to >> avoid confusing. I don't understand how allowing the user to only pass the version would confuse anyone. Could you elaborate? >> 3. Names of types and maybe versions can be good, but

Re: [openstack-dev] [Heat] A prototype for cross-vm synchronization and communication

Hi Lakshminarayanan, Seems like a solid plan. I'm probably wrong here but ain't this too tied to chef? I believe the solution should equally be suitable for chef, puppet, SaltStack, Murano, or maybe all I need is just a plain bash script execution. It may be difficult to intercept script reads the

[openstack-dev] Neutron - an issue regarding what API to follow

Hi, The API document is the official one, and Wiki is used during the development. We may be better to add a note to the wiki page to avoid such confusion. I am not sure what confused you. Could you give me an example? Thanks, Akihiro 2013年10月21日月曜日 GROSZ, Maty (Maty) maty.gr...@alcatel-lucent.

Re: [openstack-dev] Gerrit tools

On Mon, Oct 21, 2013 at 3:03 PM, Flavio Percoco wrote: > Also realize that OpenStack maintains gerritlib - >> https://github.com/openstack-**infra/gerritlib >> >> Which anyone can contribute to (and is the code that every message posted >> back to ger

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Sat, 2013-10-19 at 08:24 -0400, Monty Taylor wrote: > > On 10/19/2013 05:49 AM, Michael Still wrote: > > On Sat, Oct 19, 2013 at 7:52 PM, Clint Byrum wrote: > > > >> I suggest that we just put Copyright headers back in the source files. > >> That will make Debian's licensecheck work fairly au

Re: [openstack-dev] [novaclient]should administrator can see all servers of all tenants by default?

On Mon, Oct 21, 2013 at 1:32 AM, Lingxian Kong wrote: > two questions here: > 1. whther '--all-tenants' should be with '--tenant' or not. > 2. can admin see other tenant's server using its name instead of id? > > I think a name search as well as id makes sense, though that change lies entirely wi

[openstack-dev] [nova] resource tracking

Hi, I have encountered a few issues regarding the resource tracking and hopefully someone can help clarify here. From what I understand we just seem to ignore the actual used disk and memory from the hypervisor and calculate it according to the allocated instances. For example, if the hypervisor

Re: [openstack-dev] Gerrit tools

On 21/10/13 07:44 -0400, Sean Dague wrote: On 10/21/2013 04:04 AM, Flavio Percoco wrote: On 20/10/13 05:01 +, Joshua Harlow wrote: I created some gerrit tools that I think others might find useful. https://github.com/harlowja/gerrit_view I worked on this Python library for Gerrit[0] a c

[openstack-dev] Neutron - an issue regarding what API to follow

Hey *, I got a little confused with what API should we follow regarding Neutron VPN service... There is this wiki page https://wiki.openstack.org/wiki/Neutron/VPNaaS that handles VPN APIs, where as the formal Neutron API documentation, http://docs.openstack.org/api/openstack-network/2.0/content/

Re: [openstack-dev] [Heat] A prototype for cross-vm synchronization and communication

Hi Lakshmi, you mentioned an example in your original post, but I did not find it. Can you add the example? Lakshminaraya Renganarayana wrote on 18.10.2013 20:57:43: > From: Lakshminaraya Renganarayana > To: OpenStack Development Mailing List , > Date: 18.10.2013 21:01 > Subject: Re: [openstack

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On Sun, Oct 20, 2013 at 6:38 AM, Jeremy Stanley wrote: > On 2013-10-20 20:57:56 +0800 (+0800), Thomas Goirand wrote: > > Well, good luck finding all the copyright holders for such a large and > > old project. It's not really practical in this case, unfortunately. > > To a great extent, the same g

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

1. Good point 2. Got this case in irc, and decided to pass type and version together to avoid confusing. 3. Names of types and maybe versions can be good, but in irc conversation rejected this case, i cant remember exactly reason. 4. Actually, "active" field in version marks it as default in ty

Re: [openstack-dev] [qa][keystone] Adding client library related tests to tempest

On 10/21/2013 05:19 AM, Steven Hardy wrote: Definitely agree we should have plenty of end-to-end tests in the gate, it's the reason we've got the scenario tests, to do exactly this kind of through testing. Ok, it seems like a potential solution which may keep all involved happy would be: - Ad

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

On Sun, Oct 20, 2013 at 12:18 PM, Tim Bell wrote: > > Is it easy ? No... it is hard, whether in an integrated test suite or on > its own > Can it be solved ? Yes, we have done incredible things with the current > QA infrastructure > Should it be split off from other testing ? No, I want EVERY co

  1   2   >