Re: [openstack-dev] [tripleo] Testing optional composable services in the CI

On 09/01/2016 05:48 PM, Emilien Macchi wrote: On Thu, Aug 25, 2016 at 9:16 AM, Steven Hardy wrote: On Wed, Aug 17, 2016 at 07:20:59AM -0400, James Slagle wrote: On Wed, Aug 17, 2016 at 4:04 AM, Dmitry Tantsur wrote: However, the current gate system

Re: [openstack-dev] [tripleo] Testing optional composable services in the CI

On Thu, Sep 1, 2016 at 11:48 AM, Emilien Macchi wrote: > On Thu, Aug 25, 2016 at 9:16 AM, Steven Hardy wrote: >> On Wed, Aug 17, 2016 at 07:20:59AM -0400, James Slagle wrote: >>> On Wed, Aug 17, 2016 at 4:04 AM, Dmitry Tantsur wrote:

[openstack-dev] [requirements][FFE] global-requirements update to positional to 1.1.1

https://review.openstack.org/366631 The combination of oslo.context 2.9.0 + positional 1.0.1 (which is the current minimum requirement) results in various unit test failures in barbican, related to parsing of request headers in generated contexts for unit testing. Updating to 1.1.1 resolves this

[openstack-dev] [OSC] Tenant Resource Cleanup

Hello, During the Mitaka cycle we merged a new feature into the python-neutronclient called 'neutron purge'. This enables a simple CLI command that deletes all of the neutron resources owned by a given tenant. It's documented in the networking guide[1]. We did this in response to feedback

[openstack-dev] [javascript] [fuel-ui] Is ReactJS OSI Compliant?

Preface: IANAL (I-am-not-a-lawyer). ReactJS claims to be BSD licensed. However, it has a non-BSD patent rider with a very aggressive "Strong Retaliation Clause", meaning that if there's ever a patent dispute between [React Project] and Facebook, the patents are revoked. This might be fine. It

Re: [openstack-dev] [nova] Next steps for resource providers work

More updates on resource providers work: Yesterday we realized that a SQL join for associating inventories with allocations and resource providers was missing a critical and clause. This was leading to allocations failing to be written when there should have been plenty of capacity. This was

Re: [openstack-dev] [nova] Bug team meeting

Le 07/09/2016 10:50, Kashyap Chamarthy a écrit : On Tue, Sep 06, 2016 at 03:41:04PM -0700, Augustina Ragwitz wrote: I should add that I also expressed interest in taking over the Bug Czar role. I've been actively involved with the bugs team since Markus revived it earlier this year. I've run

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

I prefer this. 4. Trio2o, 3 votes But I would like to make sure what this actually means more specifically. How can we define this word? openstack-to-openstack Cheers, Shinobu On Tue, Sep 6, 2016 at 9:01 PM, liukun wrote: > Triangel +1 > > At 2016-09-06 16:27:22,

[openstack-dev] [nova] Add support for tag instances when booting

Hi All, Tags for servers are supported in microversion 2.26, but currently we can only add tags to instances that are already existed in the cloud, that is, we can not set tags to instances when we boot the instances. User will have to first find the instances and then add tags with another API

Re: [openstack-dev] [nova] Bug team meeting

On Tue, Sep 06, 2016 at 03:41:04PM -0700, Augustina Ragwitz wrote: > I should add that I also expressed interest in taking over the Bug Czar > role. I've been actively involved with the bugs team since Markus > revived it earlier this year. I've run meetings when he was unavailable > and also

Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP

Hi Matt, On Tue, 2016-09-06 at 16:39 -0500, Matt Riedemann wrote: > Floating IPs aren't required in OpenStack deployments, and anyone  > running with cells v1 (Rackspace, GoDaddy, NeCTAR, CERN) doesn't use > or  > support them, at least without patching Nova. So I'm not sure what  > 'industry

[openstack-dev] [tricircle]agenda of weekly meeting Sept.7

Hello, team, Agenda of Sept.7 weekly meeting, let's continue the topics: # progress review and concerns on the features like micro versions, policy control, dynamic pod binding, cross pod L2 networking # preparation for the Tricircle splitting:

[openstack-dev] [tricircle]preparation for the Tricircle splitting

Hello, As we discussed these weeks, splitting Tricircle needs to be on the table for discussion. I prepared some topics in https://etherpad.openstack.org/p/TricircleSplitting It's also linked in the Tricircle wiki. Let's discussed how to address the challenge in the splitting. Best Regards

Re: [openstack-dev] [meghdwar] use case for meghdwar API and Wednesday meeting

For API to move cloudlets, I propose to design API which can talk directly from destination edge gateway to the source gateway, for example, Pull( srcEdgeGateway, Cloudlet). Using pull will make the destination talk to the source directly, but not to introduce any broker or coordinator for the

<    1   2