Re: [openstack-dev] Scheduler hints, API and Objects

2015-09-04 12:14 GMT+09:00 Ken'ichi Ohmichi : > Hi Andrew, > > Sorry for this late response, I missed it. > > 2015-06-25 23:22 GMT+09:00 Andrew Laski : >> I have been growing concerned recently with some attempts to formalize >> scheduler hints, both with

[openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

Hi PTLs, Here is the proposed slot allocation for every "big tent" project team at the Mitaka Design Summit in Tokyo. This is based on the requests the liberty PTLs have made, space availability and project activity & collaboration needs. We have a lot less space (and time slots) in Tokyo

Re: [openstack-dev] Scheduler hints, API and Objects

Hi Alex, Thanks for your comment. IMO, this idea is different from the extension we will remove. That is modularity for the maintenance burden. By this idea, we can put the corresponding schema in each filter. 2015年9月4日(金) 19:04 Alex Xu : > 2015-09-04 11:14 GMT+08:00 Ken'ichi

Re: [openstack-dev] [murano] [dashboard] Remove the owner filter from "Package Definitions" page

Agreed. Currently, pagination is broken on "Package definitions" page now, so removing that filter will fix it back. Also, 'Other' tab looks unhelpful, admin should indicate to witch tenant this package belongs to. This improvement will be added later. Regards, Kate. On Fri, Sep 4, 2015 at 1:06

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

On Fri, Sep 04, 2015 at 12:14:06PM +0200, Thierry Carrez wrote: > > We'll start working on laying out those sessions over the available > rooms and time slots. If you have constraints (I already know > searchlight wants to avoid conflicts with Horizon, Kolla with Magnum, > Manila with Cinder,

Re: [openstack-dev] [murano] [dashboard] Remove the owner filter from "Package Definitions" page

​+1 on this. Filtering by ownership makes sense only on Catalog view (i.e. on the page of usable apps) ​but not on the admin-like console like the list of package definitions. -- Regards, Alexander Tivelkov On Fri, Sep 4, 2015 at 12:36 PM, Dmitro Dovbii wrote: > Hi

Re: [openstack-dev] [openstack-announce] [release][nova] python-novaclient release 2.28.0 (liberty)

On 09/02/2015 05:48 PM, Matt Riedemann wrote: > > > On 9/2/2015 3:40 PM, Jeremy Stanley wrote: >> On 2015-09-02 10:55:56 -0400 (-0400), d...@doughellmann.com wrote: >>> We are thrilled to announce the release of: >>> >>> python-novaclient 2.27.0: Client library for OpenStack Compute API >> [...]

Re: [openstack-dev] Scheduler hints, API and Objects

2015-09-04 11:14 GMT+08:00 Ken'ichi Ohmichi : > Hi Andrew, > > Sorry for this late response, I missed it. > > 2015-06-25 23:22 GMT+09:00 Andrew Laski : > > I have been growing concerned recently with some attempts to formalize > > scheduler hints, both

Re: [openstack-dev] [sahara] FFE request for heat wait condition support

+1 for FFE, because of 1. Low risk of issues, fully covered with current scenario tests; 2. Implementation already on review On Fri, Sep 4, 2015 at 12:54 PM, Sergey Reshetnyak wrote: > Hi, > > I would like to request FFE for wait condition support for Heat engine.

Re: [openstack-dev] FFE Request for completion of data driven assignment testing in Keystone

Great, thanks. Henry > On 4 Sep 2015, at 09:17, Thierry Carrez wrote: > > Morgan Fainberg wrote: >> >>>I would like to request an FFE for the remaining two patches that >>>are already in review >>>(https://review.openstack.org/#/c/153897/ and >>>

[openstack-dev] [murano] [dashboard] Remove the owner filter from "Package Definitions" page

Hi folks! I want suggest you to delete owner filter (3 tabs) from Package Definition page. Previously this filter was available for all users and we agreed that it is useless. Now it is available only for admin but I think this fact still doesn't improve the UX. Moreover, this filter prevents the

[openstack-dev] [sahara] FFE request for heat wait condition support

Hi, I would like to request FFE for wait condition support for Heat engine. Wait condition reports signal about booting instance. Blueprint: https://blueprints.launchpad.net/sahara/+spec/sahara-heat-wait-conditions Spec:

Re: [openstack-dev] [openstack-announce] [release][nova] python-novaclient release 2.28.0 (liberty)

On 09/04/2015 07:15 AM, Sean Dague wrote: > On 09/02/2015 05:48 PM, Matt Riedemann wrote: >> >> >> On 9/2/2015 3:40 PM, Jeremy Stanley wrote: >>> On 2015-09-02 10:55:56 -0400 (-0400), d...@doughellmann.com wrote: We are thrilled to announce the release of: python-novaclient 2.27.0:

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

On 04/09/15 12:14 +0200, Thierry Carrez wrote: Hi PTLs, Here is the proposed slot allocation for every "big tent" project team at the Mitaka Design Summit in Tokyo. This is based on the requests the liberty PTLs have made, space availability and project activity & collaboration needs. We have

Re: [openstack-dev] [sahara] Request for Feature Freeze Exception

+1 from me. Thanks, Sergey R. 2015-09-03 23:27 GMT+03:00 Ethan Gafford : > Agreed. We've talked about this for a while, and it's very low risk. > > Thanks, > Ethan > > - Original Message - > From: "michael mccune" > To:

Re: [openstack-dev] Scheduler hints, API and Objects

Le 04/09/2015 12:18, Ken'ichi Ohmichi a écrit : Hi Alex, Thanks for your comment. IMO, this idea is different from the extension we will remove. That is modularity for the maintenance burden. By this idea, we can put the corresponding schema in each filter. While I think it could be a

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

On 09/04/2015 12:14 PM, Thierry Carrez wrote: Hi PTLs, Here is the proposed slot allocation for every "big tent" project team at the Mitaka Design Summit in Tokyo. This is based on the requests the liberty PTLs have made, space availability and project activity & collaboration needs. We have a

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

No dedicated time slot for cross-project sessions this time around? On 9/4/15 6:14 AM, Thierry Carrez wrote: > Hi PTLs, > > Here is the proposed slot allocation for every "big tent" project team > at the Mitaka Design Summit in Tokyo. This is based on the requests the > liberty PTLs have made,

Re: [openstack-dev] Scheduler hints, API and Objects

On 09/04/15 at 06:54pm, Ken'ichi Ohmichi wrote: 2015-09-04 12:14 GMT+09:00 Ken'ichi Ohmichi : Hi Andrew, Sorry for this late response, I missed it. 2015-06-25 23:22 GMT+09:00 Andrew Laski : I have been growing concerned recently with some attempts to

Re: [openstack-dev] Scheduler hints, API and Objects

Le 04/09/2015 14:57, Nikola Đipanov a écrit : On 06/25/2015 04:50 PM, Monty Taylor wrote: On 06/25/2015 10:22 AM, Andrew Laski wrote: I have been growing concerned recently with some attempts to formalize scheduler hints, both with API validation and Nova objects defining them, and want to

Re: [openstack-dev] Scheduler hints, API and Objects

On 09/04/15 at 01:57pm, Nikola Đipanov wrote: On 06/25/2015 04:50 PM, Monty Taylor wrote: On 06/25/2015 10:22 AM, Andrew Laski wrote: I have been growing concerned recently with some attempts to formalize scheduler hints, both with API validation and Nova objects defining them, and want to air

[openstack-dev] [Openstack] [Horizon] [Sahara] FFE request for Sahara unified job interface map UI

Hello all, I request a FFE for the change at: https://review.openstack.org/#/c/209683/ This change enables a significant improvement to UX in Sahara's elastic data processing flow which is already in the server and client layers of Sahara. Because it specifically aims at improving ease of use

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

On 04/09/2015 6:14 AM, Thierry Carrez wrote: Hi PTLs, Here is the proposed slot allocation for every "big tent" project team at the Mitaka Design Summit in Tokyo. This is based on the requests the liberty PTLs have made, space availability and project activity & collaboration needs. We have

Re: [openstack-dev] [puppet] hosting developer documentation on http://docs.openstack.org/developer/

On 09/03/2015 03:00 PM, Emilien Macchi wrote: > > > On 09/02/2015 02:56 PM, Emilien Macchi wrote: >> >> >> On 09/02/2015 02:48 PM, Anita Kuno wrote: >>> On 09/02/2015 02:09 PM, Emilien Macchi wrote: TL;DR, I propose to move our developer documentation from wiki to something like

Re: [openstack-dev] Scheduler hints, API and Objects

On 09/04/2015 02:31 PM, Sylvain Bauza wrote: > > > Le 04/09/2015 14:57, Nikola Đipanov a écrit : >> On 06/25/2015 04:50 PM, Monty Taylor wrote: >>> On 06/25/2015 10:22 AM, Andrew Laski wrote: I have been growing concerned recently with some attempts to formalize scheduler hints, both

[openstack-dev] This is what disabled-by-policy should look like to the user

mordred@camelot:~$ neutron net-create test-net-mt Policy doesn't allow create_network to be performed. Thank you neutron. Excellent job. Here's what that looks like at the REST layer: DEBUG: keystoneclient.session RESP: [403] date: Fri, 04 Sep 2015 13:55:47 GMT connection: close content-type:

Re: [openstack-dev] Scheduler hints, API and Objects

On 06/25/2015 04:50 PM, Monty Taylor wrote: > On 06/25/2015 10:22 AM, Andrew Laski wrote: >> I have been growing concerned recently with some attempts to formalize >> scheduler hints, both with API validation and Nova objects defining >> them, and want to air those concerns and see if others agree

Re: [openstack-dev] [Openstack] [Horizon] [Sahara] FFE request for Sahara unified job interface map UI

On 09/04/2015 10:40 AM, Ethan Gafford wrote: Hello all, I request a FFE for the change at: https://review.openstack.org/#/c/209683/ This change enables a significant improvement to UX in Sahara's elastic data processing flow which is already in the server and client layers of Sahara. Because

[openstack-dev] [Manila] Gate breakage and technical FFEs

The Manila gate is finally unblocked, thanks to the efforts of Valeriy! I see patches going in now so all of the features which were granted technical FFEs should start merging IMMEDIATELY. By my calculations, we lost approximately 30 hours of time to merge stuff before the scheduled feature

[openstack-dev] [ptl][release] flushing unreleased client library changes

PTLs, We have quite a few unreleased client changes pending, and it would be good to go ahead and publish them so they can be tested as part of the release candidate process. I have the full list of changes for each project below, so please find yours and review them and then propose a release

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On 09/04/2015 10:55 AM, Morgan Fainberg wrote: On Sep 4, 2015, at 07:04, Monty Taylor wrote: mordred@camelot:~$ neutron net-create test-net-mt Policy doesn't allow create_network to be performed. Thank you neutron. Excellent job. Here's what that looks like at the

[openstack-dev] [DevStack][Keystone][Ironic][Swit] FYI: Defaulting to Keystone v3 API

Hi, This is email is just a FYI: Recently the patch [1] got merged in DevStack and broke the Ironic gate [2], I haven't had time to dig into the problem yet so I reverted the patch [3] to unblock our gate. The work to convert to v3 seems to be close enough but not yet there so I just want to

[openstack-dev] [Congress] bugs for liberty release

Hi all, I've found a few bugs that we could/should fix by the liberty release. I tagged them with "liberty-rc". If we could all pitch in, that'd be great. Let me know which ones you'd like to work on so I can assign them to you in launchpad.

Re: [openstack-dev] [Glance] Feature Freeze Exception proposal

Hi Malini et.al., We had a sync up earlier today on this topic and a few items were discussed including new comments on the spec and existing code proposal. You can find the logs of the conversation here [1]. There are 3 main outcomes of the discussion: 1. We hope to get a commitment on the

Re: [openstack-dev] [DevStack][Keystone][Ironic][Swit][Barbican] FYI: Defaulting to Keystone v3 API

This change also affected Barbican too, but they quickly tossed up a patch to resolve the gate failures [1]. As much as I would like DevStack and OpenStackClient to default to Keystone's v3 API, we should - considering how close we are in the schedule, revert the initial patch (which I see sdague

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

> On Sep 4, 2015, at 07:04, Monty Taylor wrote: > > mordred@camelot:~$ neutron net-create test-net-mt > Policy doesn't allow create_network to be performed. > > Thank you neutron. Excellent job. > > Here's what that looks like at the REST layer: > > DEBUG:

Re: [openstack-dev] [sahara] FFE request for heat wait condition support

makes sense to me, +1 mike On 09/04/2015 06:37 AM, Vitaly Gridnev wrote: +1 for FFE, because of 1. Low risk of issues, fully covered with current scenario tests; 2. Implementation already on review On Fri, Sep 4, 2015 at 12:54 PM, Sergey Reshetnyak

Re: [openstack-dev] FFE Request for completion of data driven assignment testing in Keystone

Henry, I've applied the -2 (for Feature Freeze) to a bunch of patchsets, I think I excluded your testing ones, but if the testing ones got -2'd please let me know so I can remove the -2. --Morgan On Fri, Sep 4, 2015 at 2:07 AM, Henry Nash wrote: > Great, thanks. > >

Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

On 09/04/2015 12:39 PM, Doug Hellmann wrote: PTLs, We have quite a few unreleased client changes pending, and it would be good to go ahead and publish them so they can be tested as part of the release candidate process. I have the full list of changes for each project below, so please find

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On 2015-09-04 12:50 PM, Monty Taylor wrote: > On 09/04/2015 10:55 AM, Morgan Fainberg wrote: >> >> Obviously the translation of errors >> would be more difficult if the enforcer is generating messages. > > The type: "PolicyNotAuthorized" is a good general key. Also - even > though the command I

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

Some thought has been given to this. See https://bugs.launchpad.net/neutron/+bug/1460177 I like the third option, a well-known name using DNS. On Thu, Sep 03, 2015, Kevin Benton wrote: > I think that's different than what is being asked here. That patch appears to > just add

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

On Fri, Sep 04, 2015 at 01:52:41PM +0200, Dmitry Tantsur wrote: > On 09/04/2015 12:14 PM, Thierry Carrez wrote: > >Hi PTLs, > > > >Here is the proposed slot allocation for every "big tent" project team > >at the Mitaka Design Summit in Tokyo. This is based on the requests the > >liberty PTLs have

Re: [openstack-dev] custom lbaas driver

Hello, I am trying to write an custom lbaas v2.0 driver. Was wondering if there's a document on how to go about that. I see a number of implementations as part of the source code but they all seem to be different. For instance HAProxy is completely different when compared to the other vendors. I

Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

Excerpts from Ben Swartzlander's message of 2015-09-04 14:51:10 -0400: > On 09/04/2015 12:39 PM, Doug Hellmann wrote: > > PTLs, > > > > We have quite a few unreleased client changes pending, and it would > > be good to go ahead and publish them so they can be tested as part > > of the release

Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

Excerpts from Ihar Hrachyshka's message of 2015-09-04 21:07:47 +0200: > > On 04 Sep 2015, at 18:39, Doug Hellmann wrote: > > > > > > PTLs, > > > > We have quite a few unreleased client changes pending, and it would > > be good to go ahead and publish them so they can be

Re: [openstack-dev] [Manila] Gate breakage and technical FFEs

On 09/04/2015 12:36 PM, Ben Swartzlander wrote: The Manila gate is finally unblocked, thanks to the efforts of Valeriy! I see patches going in now so all of the features which were granted technical FFEs should start merging IMMEDIATELY. By my calculations, we lost approximately 30 hours of

[openstack-dev] [nova][i18n] Is there any point in using _() in python-novaclient?

I noticed this today: https://review.openstack.org/#/c/219768/ And it got me thinking about something I've wondered before - why do we even use _() in python-novaclient? It doesn't have any .po files for babel message translation, it has no babel config, there is nothing in setup.cfg about

[openstack-dev] [app-catalog] App Catalog IRC meeting minutes - 9/3/2015

We had a good meeting yesterday which included a little cheer for the Community App Catalog project being accepted into the big tent (thanks to everyone who has been supporting our efforts all along!) The bulk of the meeting was then devoted to discussing our plans for the next generation of the

[openstack-dev] [Glance] Liberty RC reviews

Hi all, Please take some time to go through the etherpad I've created to prioritize reviews needed for Liberty RC period. These reviews have been categorized to help pick your favorite but all of them are important. As we have a decent amount of time to identify bugs and fix them, reviewing the

Re: [openstack-dev] [Manila] Gate breakage and technical FFEs

On 09/04/2015 12:36 PM, Ben Swartzlander wrote: The Manila gate is finally unblocked, thanks to the efforts of Valeriy! I see patches going in now so all of the features which were granted technical FFEs should start merging IMMEDIATELY. By my calculations, we lost approximately 30 hours of

[openstack-dev] FFE Request for moving inherited assignment to core in Keystone

Keystone has, for a number of releases, supported the concept of inherited role assignments via the OS-INHERIT extension. At the Keystone mid-cycle we agreed moving this to core this was a good target for Liberty, but this was held by needing the data driver testing to be in place

Re: [openstack-dev] [TripleO] Status of CI changes

On Thu, Sep 3, 2015 at 2:34 AM, Derek Higgins wrote: > Hi All, > > The patch to reshuffle our CI jobs has merged[1], along with the patch to > switch the f21-noha job to be instack based[2] (with centos images). > > So the current status is that our CI has been removed from

[openstack-dev] 9/4 state of the gate

There are a few things blowing up in the last 24 hours so might as well make people aware. 1. gate-tempest-dsvm-large-ops was failing at a decent rate: https://bugs.launchpad.net/nova/+bug/1491949 Turns out devstack was changed to run multihost=true and that doesn't work so well with the

Re: [openstack-dev] [neutron] pushing changes through the gate

I would like to second everything Armando has said below. Please, Neutron core reviewers, follow the advice below for the rest of the Liberty cycle as we work to merge patches targeted at Liberty. I'd also like to thank Armando for jumping in and running things the past week while I was on a

[openstack-dev] [neutron] FFE process for Liberty

Folks, Armando did a great job targeting things which missed Liberty-3 towards Liberty-RC1 here [1]. For the most part, I hope most of those will land in the coming week or so, so lets work as a team to land those. For things which are not already targeted there (or were targeted by someone else,

Re: [openstack-dev] cloud-init IPv6 support

Right, it depends on your perspective of who 'owns' the API. Is it cloud-init or EC2? At this point I would argue that cloud-init is in control because it would be a large undertaking to switch all of the AMI's on Amazon to something else. However, I know Sean disagrees with me on this point so

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

Thanks for pointing that out. I like the DNS option too. That has to be done carefully though to make sure it's not easy for an attacker to get the name of the DNS entry that the instance tries to look up. On Fri, Sep 4, 2015 at 10:53 AM, Henry Gessau wrote: > Some thought has

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On Fri, Sep 4, 2015 at 11:35 AM, Mathieu Gagné wrote: > On 2015-09-04 12:50 PM, Monty Taylor wrote: > > On 09/04/2015 10:55 AM, Morgan Fainberg wrote: > >> > >> Obviously the translation of errors > >> would be more difficult if the enforcer is generating messages. > > > >

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On Fri, Sep 4, 2015 at 10:35 AM, Mathieu Gagné wrote: > On 2015-09-04 12:50 PM, Monty Taylor wrote: > > On 09/04/2015 10:55 AM, Morgan Fainberg wrote: > >> > >> Obviously the translation of errors > >> would be more difficult if the enforcer is generating messages. > > > >

Re: [openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

On Aug 27, 2015, at 10:48 AM, Everett Toews wrote: > Hi All, > > The following API guidelines are ready for cross project review. They will be > merged on Sept. 4 if there's no further feedback. > > 1. Add description of pagination parameters >

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On 09/04/2015 01:42 PM, John Griffith wrote: On Fri, Sep 4, 2015 at 11:35 AM, Mathieu Gagné wrote: On 2015-09-04 12:50 PM, Monty Taylor wrote: On 09/04/2015 10:55 AM, Morgan Fainberg wrote: Obviously the translation of errors would be more difficult if the enforcer is

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On 2015-09-04 2:41 PM, Monty Taylor wrote: > On 09/04/2015 01:42 PM, John Griffith wrote: >> >> ​Is no good? You would like to see "less" in the output; like just the >> command name itself and "Policy doesn't allow"? >> >> To Mathieu's point, fair statement WRT the visibility of the policy name.

Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

> On 04 Sep 2015, at 18:39, Doug Hellmann wrote: > > > PTLs, > > We have quite a few unreleased client changes pending, and it would > be good to go ahead and publish them so they can be tested as part > of the release candidate process. I have the full list of changes

Re: [openstack-dev] FFE Request for moving inherited assignment to core in Keystone

-1 Unless there's something more to this, I don't think it's worth any sort of risk to stability just to shuffle API implementations around that can't wait for mikata. On Fri, Sep 4, 2015 at 12:28 PM, Henry Nash wrote: > Keystone has, for a number of releases,

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

Adding a dns server adds more complexity into the mix. You need to support both a dns server and a metadata server at that point. From: Kevin Benton [blak...@gmail.com] Sent: Friday, September 04, 2015 1:25 PM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [puppet] hosting developer documentation on http://docs.openstack.org/developer/

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2015 09:28 AM, Emilien Macchi wrote: > > > On 09/03/2015 03:00 PM, Emilien Macchi wrote: >> >> >> On 09/02/2015 02:56 PM, Emilien Macchi wrote: >>> >>> >>> On 09/02/2015 02:48 PM, Anita Kuno wrote: On 09/02/2015 02:09 PM, Emilien

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

Nikhil Komawar wrote: > No dedicated time slot for cross-project sessions this time around? That's on the Tuesday. 3 parallel sessions all day. In addition, the Ops track runs on Tuesday and Wednesday. -- Thierry Carrez (ttx)

[openstack-dev] [keystone] FFE Request for Reseller

Hi Folks, As you may know, the Reseller Blueprint was proposed and approved in Kilo ( https://review.openstack.org/#/c/139824/) with the developing postponed to Liberty. During this time, the 3 main patches of the chain were split into 8, becoming smaller and easier to review. The first 2 of

Re: [openstack-dev] [docs][networking-sfc]

On 4 September 2015 at 15:33, Paul Carver wrote: > > Can someone from the Docs team take a look at why there isn't a docs URL > for the networking-sfc repo? > Everything in OpenStack is code driven. And doc publishing happens through code review as much as anything else.

Re: [openstack-dev] 9/4 state of the gate

On 9/4/2015 3:13 PM, Matt Riedemann wrote: There are a few things blowing up in the last 24 hours so might as well make people aware. 1. gate-tempest-dsvm-large-ops was failing at a decent rate: https://bugs.launchpad.net/nova/+bug/1491949 Turns out devstack was changed to run

Re: [openstack-dev] Tracing a request (NOVA)

You may like below: https://gist.github.com/yosshy/5da0c2d6af1b446088bc Akira > Hi, > > I'm trying to trace a request made for an instance and looking at the flow > in the code. > I'm just trying to understand better how the request goes from the > dashboard to the nova-api , to the other

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On 09/04/2015 10:04 AM, Monty Taylor wrote: mordred@camelot:~$ neutron net-create test-net-mt Policy doesn't allow create_network to be performed. Thank you neutron. Excellent job. Here's what that looks like at the REST layer: DEBUG: keystoneclient.session RESP: [403] date: Fri, 04 Sep 2015

[openstack-dev] [docs][networking-sfc]

Can someone from the Docs team take a look at why there isn't a docs URL for the networking-sfc repo? Compare [1] vs [2] The first URL appears to be a rendering of the docs/source/index.rst from the Neutron Git repo, but the second one gives a Not Found even though there is a

Re: [openstack-dev] [infra][third-party][CI] Third-party oses in devstack-gate

On 01.09.2015 12:28, Evgeny Antyshev wrote: Hello! This letter I address to those third-party CI maintainers who needs to amend the upstream devstack-gate to satisfy their environment. Some folks that I know use inline patching at job level, some make private forks of devstack-gate (I even

Re: [openstack-dev] [Openstack-operators] [Neutron] Allowing DNS suffix to be set per subnet (at least per tenant)

> On 04 Sep 2015, at 08:14, Daniel Comnea wrote: > > Kevin, > > am i right in saying that the merge above was packaged into Liberty ? > > Any chance to be ported to Juno? > There is no chance a new feature will be backported to any stable branch, even Kilo. At least

Re: [openstack-dev] [Openstack] [ANN] OpenStack Kilo on Ubuntu fully automated with Ansible! Ready for NFV L2 Bridges via Heat!

Hi It is a pre pre pre pre pre pre pre alpha version that just installs the juno ubuntu guide until dashboard included. Block Storage Service is very important but does not work now. vCenter will be always the operating system that makes my life easyer. Today is Ubuntu. The hypervisor is

Re: [openstack-dev] [Openstack-operators] [Neutron] Allowing DNS suffix to be set per subnet (at least per tenant)

Kevin, am i right in saying that the merge above was packaged into Liberty ? Any chance to be ported to Juno? Cheers, Dani On Fri, Sep 4, 2015 at 12:21 AM, Kevin Benton wrote: > Support for that blueprint already merged[1] so it's a little late to > change it to

[openstack-dev] What's Up, Doc? 4 September, 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, This has been a fairly busy week, with Summit preparations beginning, more newly migrated RST books going live, and testing starting on the Install Guide. I've been spending time on sorting out the Liberty blueprints still outstanding,

Re: [openstack-dev] FFE Request for completion of data driven assignment testing in Keystone

Morgan Fainberg wrote: > >> I would like to request an FFE for the remaining two patches that >> are already in review >> (https://review.openstack.org/#/c/153897/ and >> https://review.openstack.org/#/c/154485/). >> These contain only test code and no functional changes, and >>

Re: [openstack-dev] [infra][third-party][CI] Third-party oses in devstack-gate

El 04/09/15 a las 08:11, Evgeny Antyshev escribió: > On 01.09.2015 12:28, Evgeny Antyshev wrote: >> Hello! >> >> This letter I address to those third-party CI maintainers who needs >> to amend >> the upstream devstack-gate to satisfy their environment. >> >> Some folks that I know use inline