Re: [openstack-dev] [Tripleo][CI] check-tripleo outage

On 27 February 2014 20:35, Robert Collins wrote: ' > Checking new instance connectivity next. DHCP is functional and no cloud-init errors, so we should be fully up. -Rob Robert Collins Distinguished Technologist HP Converged Cloud ___ OpenStack-de

Re: [openstack-dev] [Tripleo][CI] check-tripleo outage

On 27 February 2014 15:55, Derek Higgins wrote: > On 25/02/14 00:08, Robert Collins wrote: >> Today we had an outage of the tripleo test cloud :(. >> >> tl;dr: >> - we were down for 14 hours >> - we don't know the fundamental cause >> - infra were not inconvenienced - yaaay >> - its all ok now

Re: [openstack-dev] [Mistral] What is the model?

On 27 Feb 2014, at 08:11, Dmitri Zimine wrote: > As a learning exercise, I was trying to extract the intend behind the DSL and > current code. Giving that many things are still moving, I filled up the > blanks with imagination. Here is my understanding on where you are going: > > https://do

[openstack-dev] [cinder-client][backup]Reviews needed for backup-show bug

Hi all, I posted review for cinder backup bugs. It raises inproper exceptions like 'list() got an unexpected keyword argument 'search_opts'' when we try to show backup which doesn't exist. https://review.openstack.org/#/c/74880/ Moreever, I plan to add filter options to backup list. Below is

Re: [openstack-dev] [Tripleo][CI] check-tripleo outage

Looking into it now. On 27 Feb 2014 15:56, "Derek Higgins" wrote: > On 25/02/14 00:08, Robert Collins wrote: > > Today we had an outage of the tripleo test cloud :(. > > > > tl;dr: > > - we were down for 14 hours > > - we don't know the fundamental cause > > - infra were not inconvenienced - y

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

Michael Davies writes: > Hi everyone, > > Over in "Ironic Land" we're looking at removing XML support from ironic-api > (i.e. https://bugs.launchpad.net/ironic/+bug/1271317) > > I've been looking, but I can't seem to find an easy way to modify the > accepted content_types. > > Are there any wsgi

Re: [openstack-dev] [Mistral] Understanding parameters for tasks and actions

On 26 Feb 2014, at 16:30, Dmitri Zimine wrote: > My understanding, correct me if I'm missing the intention: > > Action are defined as code, aka REST_API or SEND_EMAIL. > These are base actions, they are analogous to function definitions. > > Tasks is a set of parameters for the action. > >

[openstack-dev] AUTO: Alexandra Shulman-Peleg is out of the office. (returning 04/03/2014)

I am out of the office until 04/03/2014. I am out of office. If required, please contact my manager Dalit Naor (da...@il.ibm.com). Note: This is an automated response to your message "[openstack-dev] [Trove] datastore version-specific disk-image-builder element" sent on 27/02/2014 0:07:2

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Hi Youcef, The point is to be able to share IP address, it really means that two VIPs(as we understand them in current model) need to reside within same backend (technically they need to share neutron port). We decided not to expose any 'colocation hint' (like loadbalancer_id) in the API, so we re

[openstack-dev] [nova] offline check inconsistent configuration during compute and api nodes

According to https://bugs.launchpad.net/nova/+bug/1270726 We might have several API node and lot of compute nodes in a cloud, for example, nova configuration assume instance_name_template should be same in all nodes; otherwise there is a potential issue as the bug indicated. I analyzed and I thin

Re: [openstack-dev] [Nova][VMWare] VMware VM snapshot

Hi Gary, I notice a new blueprint is opened last night by somebody, which is very similar with my question. https://blueprints.launchpad.net/nova/+spec/driver-specific-snapshot Could you please have a quick look and share your position for this blueprint? Thanks! On Wed, Feb 26, 2014 at 3:20 PM,

Re: [openstack-dev] [nova] [glance] [heat] bug 1203680 - fix requires doc

Dean Troyer wrote on 02/26/2014 03:28:04 PM: > On Wed, Feb 26, 2014 at 1:09 PM, Mike Spreitzer wrote: >> Thanks for the further updates. I have just one question about >> those. One way to do both unit testing and system (integration) >> testing is to: git clone your favorite project to mak

[openstack-dev] WSME / Pecan and only supporting JSON?

Hi everyone, Over in "Ironic Land" we're looking at removing XML support from ironic-api (i.e. https://bugs.launchpad.net/ironic/+bug/1271317) I've been looking, but I can't seem to find an easy way to modify the accepted content_types. Are there any wsgi / WSME / Pecan experts out there who can

[openstack-dev] [Neutron][IPv6] BP:Store both IPv6 LLA and GUA address on router interface port

As the follow up action of IPv6 sub-team meeting [1], I created a new blueprint [2] to store both IPv6 LLA and GUA address on router interface port. Here is what it's about: Based on the two modes (ipv6-ra-mode and ipv6-address-mode) design[3], RA can be sent from both openstack controlled dnsmas

Re: [openstack-dev] [Mistral] Defining term DSL

On 26 Feb 2014, at 22:54, Dmitri Zimine wrote: > Based on the terminology from [1], it's not part of the model, but the > language that describes the model in the file. Sorry, I’m having a hard time trying to understand this phrase :) What do you mean by “model” here? And why should DSL be a

Re: [openstack-dev] [nova] Future of the Nova API

On Wed, 26 Feb 2014 14:50:46 -0800 Dan Smith wrote: > > I disagree. If the client declares support for it, I think we can very > reasonably return new stuff. > > If we take what we have today in v2 and call that 2, then we could > make novaclient send this header: > > Accept: application/json

Re: [openstack-dev] [nova] Future of the Nova API

Howdy! I’m a Product Manager for Cloud Servers at Rackspace, and wanted to add a bit to what Behrens is saying. At Rackspace, we’ve experienced something like this (if you squint and look at it sideways) in the operation of our non-OpenStack cloud (“first gen Cloud Servers”) alongside our Open

Re: [openstack-dev] [nova] Future of the Nova API

On Thu, 27 Feb 2014 03:38:25 + Kenichi Oomichi wrote: > > > > v3: This is the total new api. it's with CamelCase fixing, stronger > > input vaildation, api policy checks, and task api. > > > > v2.1: This is based on v3, we transform the v2 request into v3 > > request(then they are share same

Re: [openstack-dev] [nova] Future of the Nova API

On 02/26/2014 04:50 PM, Dan Smith wrote: So if we make backwards incompatible changes we really need a major version bump. Minor versions don't cut it, because the expectation is you have API stability within a major version. I disagree. If the client declares support for it, I think we can ver

[openstack-dev] [Mistral] Renaming "events" to "triggers" and move them out of "Workflow"

Hi team, When I tell peopleI about Mistral I always have a hard time explaining why we use term “event” for declaring ways to start workflows. For example, take a look at the following snippet: Workflow: ... events: execute_backup: type: periodic tasks: execute_backup

Re: [openstack-dev] [OpenStack][Runtime Policy] A proposal for OpenStack run time policy to manage compute/storage resource

Hi Jay, Tim, Sylvain, It is an important topic of run time monitoring and policies for management of compute/storage resources. I agree this is the kind of solution that we should learn from Vmware DRS. Regarding how the Solver Scheduler fits in, we initiated this effort to address complex con

Re: [openstack-dev] [Climate] Lease by tenants feature design

Only problem here is that we'll remove admin climate user in the future and will use only trusts, so how you'll get needed info? I think we may keep info unduplicated only in one case: use trust from admin user who marked tenant as reservable to get needed info later. In this case storing needed

[openstack-dev] [glance] Switching from sql_connection to [database] connection ?

Hi, As best I can tell, all other services now use this syntax for configuring database connections: [database] connection = sqlite:///etc,omg whereas glance appears to still use [DEFAULT] ... sql_connection = sqlite:///etc,omg Is there a plan to switch to the former during Icehouse devel

[openstack-dev] [Neutron] Does l2-pop sync fdb on agent start ?

Hi all, I found my ovs-agent has missed some tunnels on br-tun. I have l2-pop enabled, if some fdb entries is added while the agent is down, can it be added back once the agent is back ? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org ht

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

On 02/26/2014 08:25 AM, Dolph Mathews wrote: On Tue, Feb 25, 2014 at 2:38 PM, Jay Pipes > wrote: On Tue, 2014-02-25 at 11:47 -0800, Morgan Fainberg wrote: > For purposes of supporting multiple backends for Identity (multiple > LDAP, mix of LDAP and SQL, f

[openstack-dev] [State-Management] Agenda for meeting (tommorow) at 2000 UTC

Hi all, The [state-management] project team holds a weekly meeting in #openstack-meeting on thursdays, 2000 UTC. The next meeting is tommorow, 2014-02-27!!! As usual, everyone is welcome :-) Link: https://wiki.openstack.org/wiki/Meetings/StateManagement Taskflow: https://wiki.openstack.org/Task

Re: [openstack-dev] [QA] The future of nosetests with Tempest

On Feb 26, 2014 7:37 PM, "Matt Riedemann" wrote: > > > > On 2/25/2014 7:46 PM, Matt Riedemann wrote: >> >> >> >> On 2/12/2014 1:57 PM, Matthew Treinish wrote: >>> >>> On Wed, Feb 12, 2014 at 11:32:39AM -0700, Matt Riedemann wrote: On 1/17/2014 8:34 AM, Matthew Treinish wrote: >

Re: [openstack-dev] [nova] Future of the Nova API

> -Original Message- > From: Alex Xu [mailto:x...@linux.vnet.ibm.com] > Sent: Thursday, February 27, 2014 11:44 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova] Future of the Nova API > > On 2014年02月26日 18:40, Thierry Carrez wrote: > > Kenichi Oomichi wrote

Re: [openstack-dev] [QA] The future of nosetests with Tempest

On 2/25/2014 7:46 PM, Matt Riedemann wrote: On 2/12/2014 1:57 PM, Matthew Treinish wrote: On Wed, Feb 12, 2014 at 11:32:39AM -0700, Matt Riedemann wrote: On 1/17/2014 8:34 AM, Matthew Treinish wrote: On Fri, Jan 17, 2014 at 08:32:19AM -0500, David Kranz wrote: On 01/16/2014 10:56 PM, Ma

Re: [openstack-dev] GSoC 2014 shared library for vmware

Hi Masaru, Please get in touch with Arnaud (cc'ed). He has graciously stepped up as a mentor. You can also talk to people on #openstack-vmware and #openstack-Oslo IRC channels. Take a look at the code so far as well - https://github.com/openstack/oslo.vmware Thanks, Dims On Feb 26, 2014 9:26 PM,

Re: [openstack-dev] [Tripleo][CI] check-tripleo outage

On 25/02/14 00:08, Robert Collins wrote: > Today we had an outage of the tripleo test cloud :(. > > tl;dr: > - we were down for 14 hours > - we don't know the fundamental cause > - infra were not inconvenienced - yaaay > - its all ok now. Looks like we've hit the same problem again tonight, I'

Re: [openstack-dev] [stackalytics] Pull request on default_data.json (addition of a domain)

Tom, Thanks for the link & tips, I'll try with these instructions. Best regards, Yuko -Original Message- From: Tom Fifield [mailto:t...@openstack.org] Sent: Thursday, February 27, 2014 11:16 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [stackalytics] Pull reque

Re: [openstack-dev] [nova] Future of the Nova API

On 2014年02月26日 18:40, Thierry Carrez wrote: Kenichi Oomichi wrote: From: Christopher Yeoh [mailto:cbky...@gmail.com] So the problem here is what we consider a "bug" becomes a feature from a user of the API point of view. Eg they really shouldn't be passing some data in a request, but its ignored

Re: [openstack-dev] [OpenStack][Runtime Policy] A proposal for OpenStack run time policy to manage compute/storage resource

Hi Tim, I'm not sure if we can put resource monitor and adjust to solver-scheduler (Gantt), but I have proposed this to Gantt design [1], you can refer to [1] and search "jay-lau-513". IMHO, Congress does monitoring and also take actions, but the actions seems mainly for adjusting single VM netwo

[openstack-dev] GSoC 2014 shared library for vmware

Hi, I'm Masaru Nomura, an MSc student studying computing. My main interests are OS, VM and programming languages. I'm quite interested in working on an Oslo project (Implement a re-usable shared library for vmware). I've finished reading guide.md (thanks Cabrera, it's helpful to fill in gaps quic

Re: [openstack-dev] [stackalytics] Pull request on default_data.json (addition of a domain)

Hi Fukuda san, You will probably receive an automated message like this soon, but: stackforge/stackalytics uses Gerrit for code review, and does not accept pull requests on github. To commit your change, you will need to follow the instructions on the OpenStack Gerrit Workflow: https://wiki.

[openstack-dev] [stackalytics] Pull request on default_data.json (addition of a domain)

Hi, I want to add the domain of my email address onto the stackalytics "default_data.json" file. I have made the necessary additions, and created "patch-1". Can someone with the credentials approve and merge? (my ID is fukuday) Thanks in advance, Yuko _

Re: [openstack-dev] [nova] Question about USB passthrough

Yes, PCI devices like GPU or HBA are common resources, admin/user do not need to specify which device to which VM. So current PCI passthrough function can meet user scenarios. But USB devices have different user scenarios. Take USB key or USB disk as example, admin/user may need the content in

Re: [openstack-dev] [Climate] Lease by tenants feature design

I don’t think that duplicating the information in Climate is a really good idea. Why don’t let Keystone manage the tenant dates information? Moreover, we can also add that to Horizon. Then, during Lease creations, Climate should query Keystone to get the tenant dates. What do you think? From:

Re: [openstack-dev] [Ironic] review days

I wanted to take a moment first to thank all the reviewers who have been getting up early // staying late to join in these review sessions -- I believe they've been tremendously helpful in unblocking a lot of work over the last two weeks. Thanks!! I also want to remind folks that we have another o

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Hi Eugene, 1) In order to allow real multiple 'vips' per pool feature, we need the listener concept. It's not just a different tcp port, but also a protocol, so session persistence and all ssl-related parameters should move to listener. Why do we need a new 'listener' concept? Since as Sam poin

Re: [openstack-dev] [Ceilometer][SUSE] SUSE OpenStack Havana distribution is different with upstream

thanks, Vincent I already noticed that the critical bug is caused by a wrong backport, just in the 0001-enable-sql-metadata-query.patchline 124, session.flush()

Re: [openstack-dev] [nova][oslo] Changes to oslo-incubator sync workflow

GCB, Ben, Thanks for volunteering to help. GCB, reminded me that we should be doing this for python-novaclient in addition to nova itself. So that being said, as I see it here are the steps moving forward: Note: as previously mentionedin this thread there already is a team working on syncing osl

[openstack-dev] [Mistral] What is the model?

As a learning exercise, I was trying to extract the intend behind the DSL and current code. Giving that many things are still moving, I filled up the blanks with imagination. Here is my understanding on where you are going: https://docs.google.com/a/stackstorm.com/drawings/d/1qBxrmQ8F7YFlz930zE

[openstack-dev] [Neutron][IPv6]

Hi, Sean and the team: Do we have a list of code reviews and a list of BPs submitted by Neutron IPv6 sub-team targeting at Icehouse 3? Would appreciate everybody’s help to compose a list so we won’t overlook anything, especially the deadline is next Friday. Thanks! Shixiong Shixiong Shang !

Re: [openstack-dev] [nova] Future of the Nova API

Again, just another quick response, but if we can find a way to merge v2 into the current v3 code, so that we don't have dual maintenance, that would be really nice. > On Feb 26, 2014, at 5:15 PM, Christopher Yeoh wrote: > > On Wed, 26 Feb 2014 16:04:38 -0600 > Chris Behrens wrote: >> >> Thi

Re: [openstack-dev] [nova] Future of the Nova API

On Wed, 26 Feb 2014 16:04:38 -0600 Chris Behrens wrote: > > This thread is many messages deep now and I’m busy with a conference > this week, but I wanted to carry over my opinion from the other “v3 > API in Icehouse” thread and add a little to it. > > Bumping versions is painful. v2 is going to

Re: [openstack-dev] [python-*client] moving to WebOb exceptions

On Wed, Feb 26, 2014 at 5:30 PM, Alexei Kornienko < alexei.kornie...@gmail.com> wrote: > Hi, > > Could you please explain in more details what causes pain in adding > additional requirement to clients (in most cases when client is used inside > other openstack projects it's there already)? > My IM

Re: [openstack-dev] [nova] Future of the Nova API

On Wed, 26 Feb 2014 06:29:02 -0800 Dan Smith wrote: > > So I was thinking about this and Ken'ichi has basically said pretty > > much the same thing in his reply to this thread. I don't think it > > makes client moves any easier though - this is all about lowering > > our maintenance costs. > > S

[openstack-dev] packstack support for DRBD based installation

Hi , We are using packstack based openstack installation. I am working on providing HA support for Openstack services and dependent 3rd part services like mysql etc . I will be using DRBD and pacemaker based HA functionality. Is there any support for installing DRBD based installation using p

Re: [openstack-dev] [nova] Future of the Nova API

> So if we make backwards incompatible changes we really need a major > version bump. Minor versions don't cut it, because the expectation is > you have API stability within a major version. I disagree. If the client declares support for it, I think we can very reasonably return new stuff. If we

[openstack-dev] [devstack] [neutron] OpenDaylight devstack support questions

So, I have this review [1] which attempts to add support for OpenDaylight to devstack. What this currently does, in Patch 7, is that it uses the "extras" functionality of devstack to program the OVS on the host so that OpenDaylight can control it. On teardown, it does the reverse. Simple and straig

Re: [openstack-dev] [nova] Future of the Nova API

On Wed, 26 Feb 2014 11:40:25 +0100 Thierry Carrez wrote: > > We may need to differentiate between breaking the API and breaking > corner-case behavior. In one case you force everyone in the ecosystem > to adapt (the libraries, the end user code). In the other you only > (potentially) affect those

Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS

On 26/02/14 07:03 -0700, Steven Dake wrote: On 02/26/2014 06:47 AM, Charles Walker wrote: Hi, I am trying to deploy the proprietary application made in my company on the cloud. The pre requisite for this is to have a IAAS which can be either a public cloud or private cloud (openstack is an

Re: [openstack-dev] [nova][ceilometer] ceilometer unit tests broke because of a nova patch

> Ceilometer really needs to stop importing server projects in unit tests. > By nature this is just going to break all the time. i believe that was the takeaway from the thread -- it's an old thread and i was just doing some back-reading. > Cross project interactions need to be tested by someth

Re: [openstack-dev] [devstack] Bug in is_*_enabled functions?

Brian, In shell it is correct to return 0 for success and non-zero for failure. Carl On Feb 26, 2014 10:54 AM, "Brian Haley" wrote: > While trying to track down why Jenkins was handing out -1's in a Neutron > patch, > I was seeing errors in the devstack tests it runs. When I dug deeper it > lo

Re: [openstack-dev] [nova] Future of the Nova API

On Wed, 26 Feb 2014 09:28:20 -0800 Dan Smith wrote: > > > If we do go down this route of changing the v2 API like this, it > > would be nice to bump the minor version as well, so when a user has > > to distinguish between the two versions they don't have to say > > Havana V2 vs Icehouse V2, they

Re: [openstack-dev] [python-*client] moving to WebOb exceptions

Hi, Could you please explain in more details what causes pain in adding additional requirement to clients (in most cases when client is used inside other openstack projects it's there already)? My IMHO is that having to write ugly hacks to handle several exception classes with the same name causes

[openstack-dev] [Neutron] Flavor Framework

Hi neutron folks, I know that there are patches on gerrit for VPN, FWaaS and L3 services that are leveraging Provider Framework. Recently we've been discussing more comprehensive approach that will allow user to choose service capabilities rather than vendor or provider. I've started creating des

[openstack-dev] [Trove] datastore version-specific disk-image-builder element

We have a need to support multiple versions of a single datastore with a single set of disk-image-builder elements. Let's take MySQL on Ubuntu as an example. 5.5 is already present in trove-integration. Let's say we want to add 5.6 to coexist. Let's also assume that simply asking for the existin

Re: [openstack-dev] [nova] Future of the Nova API

This thread is many messages deep now and I’m busy with a conference this week, but I wanted to carry over my opinion from the other “v3 API in Icehouse” thread and add a little to it. Bumping versions is painful. v2 is going to need to live for “a long time” to create the least amount of pain

Re: [openstack-dev] [WSME] Dynamic types and POST requests

On Wed, Feb 26, 2014 at 3:34 PM, Sylvain Bauza wrote: > > > > 2014-02-26 19:40 GMT+01:00 Doug Hellmann : > > >> So you're not segregating the dynamic part of the API at all from the >> static part? >> >> Doug >> >> > No, you're right, at least with API V1 (Flask). As per our discussion, it > seems

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Hi Sam, I've looked over the document, couple of notes: 1) In order to allow real multiple 'vips' per pool feature, we need the listener concept. It's not just a different tcp port, but also a protocol, so session persistence and all ssl-related parameters should move to listener. 2) ProviderRes

Re: [openstack-dev] [devstack] Bug in is_*_enabled functions?

On 02/26/2014 01:36 PM, Dean Troyer wrote: On Wed, Feb 26, 2014 at 11:51 AM, Brian Haley mailto:brian.ha...@hp.com>> wrote: While trying to track down why Jenkins was handing out -1's in a Neutron patch, I was seeing errors in the devstack tests it runs. When I dug deeper it loo

Re: [openstack-dev] [nova][ceilometer] ceilometer unit tests broke because of a nova patch

On 02/26/2014 03:33 PM, Gordon Chung wrote: > hi, > > just so this issue doesn't get lost again. Mehdi's bp seems like a good > place to track this issue: > https://blueprints.launchpad.net/nova/+spec/usage-data-in-notification. > > Joe, i agree with you that it's too late for this iteration... m

[openstack-dev] [QA] Meeting Thursday February 27th at 17:00UTC

Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, February 27th at 17:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to add an item

Re: [openstack-dev] setting up 1-node devstack + ml2 + vxlan

Please look at my last reply. Do you have several compute nodes? If you have only one node, you won't have any vxlan port on br-tun. On Wed, Feb 26, 2014 at 6:44 PM, Varadhan, Sowmini wrote: > On 2/26/14 5:47 AM, Mathieu Rohon wrote: >> Hi, >> >> FYI setting the vxlan UDP doesn't work properly fo

Re: [openstack-dev] [WSME] Dynamic types and POST requests

2014-02-26 19:40 GMT+01:00 Doug Hellmann : > > So you're not segregating the dynamic part of the API at all from the > static part? > > Doug > > No, you're right, at least with API V1 (Flask). As per our discussion, it seems our use-case hasn't yet been implemented in WSME, so I'll provide a diffe

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On Wed, Feb 26, 2014 at 1:43 PM, Jay Dobies wrote: > > I like the notion of OpenStackClient. I'll talk ideals for a second. If we > had a standard framework and each project provided a command abstraction > that plugged in, we could pick and choose what we included under the Tuskar > umbrella. Adv

Re: [openstack-dev] [nova][ceilometer] ceilometer unit tests broke because of a nova patch

hi, just so this issue doesn't get lost again. Mehdi's bp seems like a good place to track this issue: https://blueprints.launchpad.net/nova/+spec/usage-data-in-notification. Joe, i agree with you that it's too late for this iteration... maybe it's something we should mark > low priority for J

Re: [openstack-dev] [nova] [glance] [heat] bug 1203680 - fix requires doc

On Wed, Feb 26, 2014 at 1:09 PM, Mike Spreitzer wrote: > Thanks for the further updates. I have just one question about those. > One way to do both unit testing and system (integration) testing is to: > git clone your favorite project to make a working local repo somewhere on > your testing mac

[openstack-dev] [savanna] team meeting Feb 27 1800 UTC

Hi folks, We'll be having the Savanna team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_February.2C_27 http://www.timeanddate.com/worldclock/fixedtime.html?msg=Savanna+Meeting&iso=20140227T18 The main topics are p

Re: [openstack-dev] [Mistral] Porting executor and engine to oslo.messaging

So this design is starting to look pretty familiar to a what we have in taskflow. Any reason why it can't just be used instead? https://etherpad.openstack.org/p/TaskFlowWorkerBasedEngine This code is in a functional state right now, using kombu (for the moment, until oslo.messaging becomes py3

Re: [openstack-dev] [Neutron] L3 HA VRRP concerns

Assaf, It would be helpful if these notes were on the reviews [1]. I think there are concerns in this email that I have not noticed in the review. Maybe I missed them. Carl [1] https://blueprints.launchpad.net/neutron/+spec/l3-high-availability On Mon, Feb 24, 2014 at 8:58 AM, Assaf Muller

[openstack-dev] [nova][ceph] Reviews needed for ceph rbd ephemeral bugs

Hi, I'm writing to call for some core-reviewers to give any eye to some rbd related reviews that are open. https://review.openstack.org/#/c/59149/ ^parent https://review.openstack.org/#/c/59148/ ^^parent https://review.openstack.org/#/c/33409/ Thanks, Andrew W. Mirantis. ___

Re: [openstack-dev] [TripleO] Tuskar CLI UX

Hello, i went through the CLI way of deploying overcloud, so if you're interested what's the workflow, here it is: https://gist.github.com/jistr/9228638 This is excellent to see it all laid out like this, thanks for writing it up. I'd say it's still an open question whether we'll want to g

Re: [openstack-dev] supported dependency versioning and testing

On Fri, Feb 21, 2014 at 10:17 AM, Sean Dague wrote: > On 02/21/2014 11:02 AM, Daniel P. Berrange wrote: >> On Fri, Feb 21, 2014 at 10:46:22AM -0500, Sean Dague wrote: >>> On 02/21/2014 09:45 AM, Daniel P. Berrange wrote: On Thu, Feb 20, 2014 at 02:45:03PM -0500, Sean Dague wrote: > >

[openstack-dev] [Neutron][FYI] Bookmarklet for neutron gerrit review

Hi folks I wrote an bookmarklet for neutron gerrit review. This bookmarklet make the comment title for 3rd party ci as gray. javascript:(function(){list = document.querySelectorAll('td.GJEA35ODGC'); for(i in list){if(!list[i].innerHTML){continue;};if(list[i].innerHTML && list[i].innerHTML.search(

Re: [openstack-dev] [TripleO][Tuskar] JSON output values from Tuskar API

This is a new concept to me in JSON, I've never heard of a wrapper element like that being called a namespace. My first impression is that is looks like cruft. If there's nothing else at the root of the JSON document besides the namespace, all it means is that every time I go to access relevan

[openstack-dev] Savanna graduation status

Hi folks, I'd like to follow-up Savanna graduation status. All requirements listed in the [0] has been solved. You can find details in [1]. So, I'd like to ask for Savanna graduation review topic addition to the TC meetings backlog. :) All questions raised on the incubation review were covered o

Re: [openstack-dev] [nova] [glance] [heat] bug 1203680 - fix requires doc

Dean Troyer wrote on 02/26/2014 12:53:31 PM: > Thanks for the updates, but I've massaged the project bits and > restored/expanded the reasons to consider one or the other option. Thanks for the further updates. I have just one question about those. One way to do both unit testing and system (

[openstack-dev] [Neutron][LBaaS] Enterprise Ready Features

TL;DR: Are enterprise needed features (HA, scalability, resource management, etc) on this project's roadmap. If so, how much of a priority is it? I've been doing some research on Neutron LBaaS to determine the viability and what needs to be done to allow for it to become an enterprise ready sol

Re: [openstack-dev] [Mistral] Porting executor and engine to oslo.messaging

Thanks. I'll start making the changes. The other transport currently implemented at oslo.messaging is located at https://github.com/openstack/oslo.messaging/tree/master/oslo/messaging/_drivers, prefixed with impl. There are quid and zmq. On Wed, Feb 26, 2014 at 12:03 AM, Renat Akhmerov wrote:

Re: [openstack-dev] [WSME] Dynamic types and POST requests

On Tue, Feb 25, 2014 at 5:44 PM, Sylvain Bauza wrote: > Thanks Doug for replying, > > > > 2014-02-25 23:10 GMT+01:00 Doug Hellmann : > > >> >> >>> Do you have any idea on how I could get my goal, ie. having a static >>> input plus some extra variable inputs ? I was also thinking about playing >>>

[openstack-dev] [TripleO][Tuskar] JSON output values from Tuskar API

Hi, I am wondering what is the OpenStack way of returning json from apiclient. I have got 2 different JSON response examples from http://api.openstack.org/: json output with namespace: { "volume": { "status":"available", "availability_zone":"nova", "id":"5aa119a8-d25b-45a7-8d1b-8

Re: [openstack-dev] [devstack] Bug in is_*_enabled functions?

On Wed, Feb 26, 2014 at 11:51 AM, Brian Haley wrote: > While trying to track down why Jenkins was handing out -1's in a Neutron > patch, > I was seeing errors in the devstack tests it runs. When I dug deeper it > looked > like it wasn't properly determining that Neutron was enabled - > ENABLED_S

Re: [openstack-dev] [python-*client] moving to WebOb exceptions

On Wed, Feb 26, 2014 at 11:20 AM, Andrey Kurilin wrote: > While working on unification of clients code we try to unify various > exceptions in different client projects. > We have module apiclient.exceptions in oslo-incubator[1]. Since our > apiclient is an oslo-inclubator library and not a standa

Re: [openstack-dev] [nova] [glance] [heat] bug 1203680 - fix requires doc

On Wed, Feb 26, 2014 at 12:53 AM, Mike Spreitzer wrote: > (I added some tags in the subject line, probably should have been there > from the start.) > > Thanks guys, for an informative discussion. I have updated > https://wiki.openstack.org/wiki/Gerrit_Workflow and > https://wiki.openstack.org/wi

[openstack-dev] [devstack] Bug in is_*_enabled functions?

While trying to track down why Jenkins was handing out -1's in a Neutron patch, I was seeing errors in the devstack tests it runs. When I dug deeper it looked like it wasn't properly determining that Neutron was enabled - ENABLED_SERVICES had multiple "q-*" entries, but 'is_service_enabled neutron

Re: [openstack-dev] [OpenStack][Runtime Policy] A proposal for OpenStack run time policy to manage compute/storage resource

Hi Jay and Sylvain, The solver-scheduler sounds like a good fit to me as well. It clearly provisions resources in accordance with policy. Does it monitor those resources and adjust them if the system falls out of compliance with the policy? I mentioned Congress for two reasons. (i) It does mo

Re: [openstack-dev] Hacking and PEP 257: Extra blank line at end of multi-line docstring

On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote: > On 02/26/2014 11:40 AM, Joe Gordon wrote: > >> This is missing the point about manually enforcing style. If you pass >> the 'pep8' job there is no need to change any style. > > > In a perfect world, yes. While there are exceptions to this, t

Re: [openstack-dev] setting up 1-node devstack + ml2 + vxlan

On 2/26/14 5:47 AM, Mathieu Rohon wrote: > Hi, > > FYI setting the vxlan UDP doesn't work properly for the moment : > https://bugs.launchpad.net/neutron/+bug/1241561 So I checked this again by going back to 13.10, still no luck. > > May be your kernel has the vxlan module already loaded, which bi

Re: [openstack-dev] sqlalchemy-migrate release impending

On 02/26/2014 11:24 AM, David Ripton wrote: > I'd like to release a new version of sqlalchemy-migrate in the next > couple of days. The only major new feature is DB2 support. If anyone > thinks this is a bad time, please let me know. > So it would be nice if someone could actually work through

Re: [openstack-dev] [nova] Future of the Nova API

> Users actually care about the latter. If the API accepts 'red' as a > valid UUID then that is part of the implicit contract. Yeah, but right now, many of those things are "would fail on postgres and succeed on mysql" (not uuids necessarily, but others). Since we can't honor them in all cases, I

[openstack-dev] [python-*client] moving to WebOb exceptions

Hi, While working on unification of clients code we try to unify various exceptions in different client projects. We have module apiclient.exceptions in oslo-incubator[1]. Since our apiclient is an oslo-inclubator library and not a standalone lib this doesn't help in case we need to process except

Re: [openstack-dev] [nova] Future of the Nova API

On Wed, Feb 26, 2014 at 6:38 AM, Dan Smith wrote: >> We may need to differentiate between breaking the API and breaking >> corner-case behavior. > > Totally agreed. > >> In one case you force everyone in the ecosystem to >> adapt (the libraries, the end user code). In the other you only >> (potent

Re: [openstack-dev] bug 1203680 - fix requires doc

On Tue, Feb 25, 2014 at 12:01 PM, Ben Nemec wrote: > So is there some git magic that also keeps the repos in sync, or do you > have to commit/pull/restart service every time you make changes? I ask > because experience tells me I would inevitably forget one of those steps at > some point and be

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Hi, I have added to the wiki page: https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance/Discussion#1.1_Turning_existing_model_to_logical_model that points to a document that includes the current model + L7 + SSL. Please review. Regards, -Sam. From: Samuel Bercovi

Re: [openstack-dev] Hacking and PEP 257: Extra blank line at end of multi-line docstring

On 02/26/2014 11:40 AM, Joe Gordon wrote: This is missing the point about manually enforcing style. If you pass the 'pep8' job there is no need to change any style. In a perfect world, yes. In the real world, there are several things in PEP8 or our project guidelines that the tools don't enf

Re: [openstack-dev] [neutron]Can somebody describe the all the rolls about networks' admin_state_up

- Original Message - > A thread [1] was also initiated on the ML by Syvlain but no answers/comment > for the moment. > > [1] http://openstack.markmail.org/thread/qy6ikldtq2o4imzl > > Édouard. > IMHO admin_state_up = false should bring the network down and the traffic needs to be stop

  1   2   >