Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

Do we have any success here.. ? On Mon, Jul 20, 2015 at 8:32 AM Alex Schultz wrote: > Vladimir, > > Thanks. Can you point me to the error for perestroika? I'd be happy to > take a look as well. I spent most of Friday throwing various options at the > CI system to try and figure out how to get t

Re: [openstack-dev] [Fuel] 7.0 Release - Feature Freeze in action

Thanks Eugene! Congratulations everyone. It was not easy, but we got all essential features merged except a couple of more or less minor parts from them, which require exceptions. Unfortunately, some High priority blueprints didn't make it. Let's see what do we do about exceptions requests. Thank

[openstack-dev] [all] cross project communication: Return request-id to caller

Hi Devs, X-Openstack-Request-Id. We have analysed python-cinderclient, python-glanceclient, python-novaclient, python-keystoneclient and python-neutronclient to check the return types. There are 9 ways return values are returned from python clients: 1. List 2. Dict 3. Resource class object 4. N

Re: [openstack-dev] [Cinder] FFE Request: Re-add Quobyte Cinder Driver

Hello Mike, Hello Cinder Community! After finding solutions for the two aforementioned bugs the Quobyte Cinder CI has now been reporting without finding further blocking issues. I triggered a range of rechecks in the last days that the CI has been working on in the last ~36h. Please review if thes

Re: [openstack-dev] [fuel] FF Exception request for Fernet tokens support.

Fuel Library team, I expect your immediate reply here. I'd like upgrades team to take a look at this one, as well as at the one which moves Keystone under Apache, in order to check that there are no issues here. -1 from me for this time in the cycle. I'm concerned about: 1. I don't see any re

Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

On 07/24/2015 12:59 PM, Zaro wrote: Hello Tang, Openstack slaves only have a single executor so what you are probably seeing is due to using build slaves that have multiple executors. There were a few bugs[1] that was fixed recently around these types of deadlock issues. The new gearman-plug

Re: [openstack-dev] [Fuel] Restore OSD devices with Puppet Ceph module

On Wed, Jul 22, 2015 at 3:52 PM, Oleg Gelbukh wrote: > Greetings, > > While working on upgrade of OpenStack with Fuel installer, I meet a > requirement to re-add OSD devices with the existing data set to a Ceph > cluster using Puppet module. Node is reinstalled during the upgrade, thus > disks us

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Custom node attributes feature

Colleagues, it sounds like we need to complete what was requested by Julia here (and it would take about a day as I understand), plus Andrey's request (which seems to be very important for partner story and flexibility), plus additional pieces which turned into bugs [1]. I'd like to hear opinion f

Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

Hello Tang, Openstack slaves only have a single executor so what you are probably seeing is due to using build slaves that have multiple executors. There were a few bugs[1] that was fixed recently around these types of deadlock issues. The new gearman-plugin release[2] contains fixes for those i

Re: [openstack-dev] [keystone] LDAP identity driver with groups from local DB

The LDAP driver for identity shouldn't require write access to look up groups. It'll only require write access if you want to allow Keystone to create/delete/update new groups. Not sure what you mean by "requires an LDAP admin to set up groups separately" either. Have any more details you can share

Re: [openstack-dev] [keystone] LDAP identity driver with groups from local DB

Julian, You want this hybrid backend driver. Bind against LDAP for auth, store everything else in mysql: https://github.com/SUSE-Cloud/keystone-hybrid-backend We maintain our own fork with has a few small differences. I do not use the assignment portion of the driver and I'm not sure anyone does

Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

On 07/24/2015 12:00 PM, Tang Chen wrote: On 07/24/2015 10:08 AM, Tang Chen wrote: On 07/23/2015 11:44 PM, Asselin, Ramy wrote: Are you running on 'master' nodes? I remember seeing an issue where with a recent version of Jenkins or a plugin where it doesn't execute jobs on the master node.

Re: [openstack-dev] [fuel][puppet] Module Sync for Murano and Sahara

On Thu, Jul 23, 2015 at 8:40 PM, Andrew Woodward wrote: > Denis, > > Now that I have better understanding of the history of the commit, I > understand that this was the best way through. The Sahara and Murano team's > effort was invaluable in getting these fixed up and in a good state. I > apolog

Re: [openstack-dev] [fuel][puppet] Module Sync for Murano and Sahara

On Wed, Jul 22, 2015 at 9:48 AM, Denis Egorenko wrote: > Hi Andrew! > > Sahara already merged. All CI tests were succeeded, also was built custom > iso [1] and ran bvt tests [2], which also were succeeded and we got +1 from > QA team. > For Murano we will do the same: resolve all comments, build

[openstack-dev] [keystone] LDAP identity driver with groups from local DB

Hello, I am relatively new to Openstack and Keystone so please forgive me any crazy misunderstandings here. One of the problems with the existing LDAP Identity driver that I see is that for group management it needs write access to the LDAP server, or requires an LDAP admin to set up groups separ

Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

On 07/24/2015 10:08 AM, Tang Chen wrote: On 07/23/2015 11:44 PM, Asselin, Ramy wrote: Are you running on 'master' nodes? I remember seeing an issue where with a recent version of Jenkins or a plugin where it doesn't execute jobs on the master node. But when run on non-master jenkins slaves,

[openstack-dev] [app-catalog] Catalog roadmap and next steps

We have been making some progress on improvements to the Community App Catalog, but this last month things have slowed down some. I wanted to send a note to the mailing list to get a conversation going about what we need to get on the roadmap, and hopefully get some folks committed to helping out.

[openstack-dev] What's Up, Doc? 24 July 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, Wow! What a great week for RST conversion patches! As I write this, there are only a handful of outstanding sections on the Cloud Admin and HA Guides, and well over 40 sections have now been converted on the Install Guide, with the conver

[openstack-dev] [Neutron][SFC] Launchpad cleanup

Is it possible to delete dead blueprints or at least change the section at the top to just provide a URL to the blueprint that supersedes it? Blueprint [1] links to a bunch of abandoned reviews and references its parent Blueprint [2] which also links to abandoned work. The current work on serv

Re: [openstack-dev] [Neutron][SFC] Wiki update - deleting old SFC API

On a general topic of wiki cleanup, what's the preferred mechanism for documenting APIs? Wiki page [1] largely duplicates the content of the spec in [2] I dislike duplication of information because it's likely to get out of sync. I'd rather use hyperlinks whenever possible. However, linking to

Re: [openstack-dev] [nova][v2.1 api calls]

Thanks Ed for the explanation what is the meaning of contained support. api calls, for example GET /v2.1/os-quota-sets/​{tenant_id}​} was not working. But /v3/os-quota-sets/​{tenant_id}​ was working fine whether I am missing something ? best

Re: [openstack-dev] [Neutron][L3] Representing a networks connected by routers

On 7/23/2015 2:45 PM, Kevin Benton wrote: We ran in to this long ago. What are some other examples? We've be good about keeping the network L2 only. Segments, VLAN transparency, and other properties of the network are all L2. The example you gave about needing the network to see the grouping o

Re: [openstack-dev] [nova][v2.1 api calls]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/23/2015 09:16 PM, Sajeesh Cimson Sasi wrote: > Can you please tell me whether nova supports v2.1 api calls now. If > so can you please tell me where the code is located.I can see the > codes for v2(quotas.py) and v3(plugin/v3/quots_sets.py). I

[openstack-dev] [Nova] Cancel Nova API meeting this week

Hi As people join mid-cycle meetup, we cancel nova API meeting this week. Thanks Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [nova][v2.1 api calls]

Hi All, Can you please tell me whether nova supports v2.1 api calls now. If so can you please tell me where the code is located.I can see the codes for v2(quotas.py) and v3(plugin/v3/quots_sets.py). I was thinking that v2.1 is equivalent to v3 calls, since the api calls are looking si

Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

On 07/23/2015 11:44 PM, Asselin, Ramy wrote: Are you running on 'master' nodes? I remember seeing an issue where with a recent version of Jenkins or a plugin where it doesn't execute jobs on the master node. But when run on non-master jenkins slaves, it works fine. I checked my configuration

Re: [openstack-dev] [neutron][lbaasv2] Radware CI failure

?Evgeny/Sam/Radware, https://os-ci-logs.radware.com/179818_27_2015-07-18_10-08-37/lbaas_v2_tempest_tests.log The test_members module changed names. Should be as easy as just renaming the import. I'd also check for other module renames as well. Thanks, Brandon _

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi Chandeep, The official dates of the meet up are When: August 05-06 2015. Where: HP Building 6 Lower level (street level) Room C6/7 (6LC7/9) 3404 E Harmony Rd (Ziegler), Fort Collins, CO 80528, United States The information is at the Etherpad. We'll probably start at around 8:30 or 9:00 AM MST

Re: [openstack-dev] [Congress] Need reviews of bp rpc-for-dse

OK, get it. -Yingxin From: Tim Hinrichs [mailto:t...@styra.com] Sent: Thursday, July 23, 2015 11:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Congress] Need reviews of bp rpc-for-dse Hi Yingxin, We definitely want details for what you have

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Custom node attributes feature

Hi, folks. I understand it may be not a good time but I want to make a proposal regarding this feature. The feature may be extremely useful for plugin developers if these labels would be serialized into astute.yaml. They may be used by plugin tasks to do node-specific modifications. Let me provide

Re: [openstack-dev] [fuel][puppet] Module Sync for Murano and Sahara

Denis, Now that I have better understanding of the history of the commit, I understand that this was the best way through. The Sahara and Murano team's effort was invaluable in getting these fixed up and in a good state. I apologize that I have raised this as an issue. I was very concerned with th

Re: [openstack-dev] [glance][api] Response when a illegal body is sent

On 07/23/2015 12:43 PM, Ryan Brown wrote: On 07/23/2015 12:13 PM, Jay Pipes wrote: On 07/23/2015 10:53 AM, Bunting, Niall wrote: Hi, Currently when a body is passed to an API operation that explicitly does not allow bodies Glance throws a 500. Such as in this bug report: https://bugs.launchpa

Re: [openstack-dev] [Neutron][L3] Representing a networks connected by routers

> IOW, I don't think what I proposed in adding L3 stuff to the network that wasn't already here. The point I'm trying to make is that there isn't any L3 stuff on the network itself. There are L3 things that depend on the network because an L2 network carries them. But the routed network proposes s

Re: [openstack-dev] [TripleO] Moving instack upstream

On Thu, Jul 23, 2015 at 2:40 AM, Derek Higgins wrote: > See below > > > On 21/07/15 20:29, Derek Higgins wrote: >> >> Hi All, >> Something we discussed at the summit was to switch the focus of >> tripleo's deployment method to deploy using instack using images built >> with tripleo-puppet-elem

Re: [openstack-dev] [nova] nova unittests will be affected by mock 1.3

On 07/23/2015 06:34 PM, Robert Collins wrote: > I've released mock 1.3 which really correctly fixes the behaviour of > mock_open. Unfortunately there is a test in nova that is faulty (and > was faulty but silently so with 1.2). > > https://review.openstack.org/204222 fixes this up. > > I had int

Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron

On Fri, Jul 24, 2015 at 12:02 AM, Mohammad Banikazemi wrote: > "Daneyon Hansen (danehans)" wrote on 07/23/2015 > 03:40:38 PM: > >> From: "Daneyon Hansen (danehans)" >> To: "OpenStack Development Mailing List (not for usage questions)" >> , Mohammad Banikazemi/Watson/ >> IBM@IBMUS, "Steven Dake (

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

Roland, Could you please specify the time of the meetup , I need to book my Airtickes accordingly On 7/23/15, 4:30 PM, "Chandeep Khamba" wrote: >Hi Roland, > >I am still a newbie to Monasca , but would like to hear and participate >in the agenda items we already have. >If I have something spe

Re: [openstack-dev] [Fuel] Question about unique default hostname for node

On Wed, Jul 22, 2015 at 6:32 AM Fedor Zhadaev wrote: > Thanks for your answers. > > Let me clarify some points: > > Sure, we have to validate hostnames during node renaming. And sure we do > it. This issue appears when we already have node with name 'node-X' and new > node is created without prov

[openstack-dev] [nova] nova unittests will be affected by mock 1.3

I've released mock 1.3 which really correctly fixes the behaviour of mock_open. Unfortunately there is a test in nova that is faulty (and was faulty but silently so with 1.2). https://review.openstack.org/204222 fixes this up. I had intended to let it land before releasing, but I forgot I had it

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi Roland, I am still a newbie to Monasca , but would like to hear and participate in the agenda items we already have. If I have something specific would definitely add it. Thanks On 7/23/15, 1:58 PM, "Hochmuth, Roland M" wrote: >Hi Chandeep, There are no fees. It would be great if you could

Re: [openstack-dev] [Neutron][L3] Representing a networks connected by routers

On Thu, Jul 23, 2015 at 1:45 PM, Kevin Benton wrote: >>We ran in to this long ago. > > What are some other examples? We've be good about keeping the network L2 > only. Segments, VLAN transparency, and other properties of the network are > all L2. Another thing is that we create floating IPs from

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

+1 2015-07-24 1:56 GMT+03:00 Sergey Vasilenko : > +1 > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

+1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Switching keystone to apache wsgi

Just to ensure that everyone knows - patch is merged. I hope that we will see performance improvements, and looking for test results :) On Thu, Jul 23, 2015 at 1:13 PM Aleksandr Didenko wrote: > Hi, > > guys, we're about to switch keystone to apache wsgi by merging [0]. Just > wanted to make sur

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

+1 -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Thu, Jul 23, 2015 at 11:48 AM, Mike Scherbakov wrote: > +1 > > On Thu, Jul 23, 2015 at 10:50 AM Evgeniy L wrote: > >> +1 >> >> On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov >> wrote: >> >>> At the moment we have several co

Re: [openstack-dev] [fuel][CI] Fuel-web CI is broken

Have we resolved this? What is the long term strategy on this? On Mon, Jul 20, 2015 at 10:51 PM Andrew Woodward wrote: > I found this after noon that fuel-web CI was broken due to the recent > release of oslo.config and oslo.utils 2.0.0 [1] > > I attempted to muck around with the pinning of the

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Deploy nova-compute (VCDriver) feature

Since we are in FF state already, I'd like to have urgent estimate from one of fuel-library cores: - holser - alex_didenko - aglarendil - bogdando aglarendil is on vacation though. Guys, please take a look at https://review.openstack.org/#/c/196114/ - can we accept it as exception? Seems to be goo

[openstack-dev] [Fuel] 7.0 Release - Feature Freeze in action

Hello everyone, Please be informed that we have officially entered Feature Freeze state for Fuel 7.0 Release. This means that since now on we focus on bugfixing and stop accepting new code except bugfix commits. If you believe that the code for your feature still needs to be merged as an excep

Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron

"Daneyon Hansen (danehans)" wrote on 07/23/2015 03:40:38 PM: > From: "Daneyon Hansen (danehans)" > To: "OpenStack Development Mailing List (not for usage questions)" > , Mohammad Banikazemi/Watson/ > IBM@IBMUS, "Steven Dake (stdake)" > Cc: Eran Gampel , Irena Berezovsky > > Date: 07/23/2015

Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron

> $ docker -d --kv-store=consul:localhost:8500 -- > label=com.docker.network.driver.kuryr.bind_interface=eth0 -- > label=com.docker.network.driver.kuryr.neutron_api=10.10.10.10 > --label=com.docker.network.driver.kuryr.token=AUTH_tk713d067336d21348bcea1ab220965485 Toni, Why do you want to have

Re: [openstack-dev] [Fuel] Get rid of fuelmenu

Hello Vladimir, from me -1. We can discuss if enable fuelmenu=yes or not in grub, but I wouldn't get rid of it. I've never heard complaints against fuelmenu from users, and it's widely used for basic settings afterinstall. If the users had to manually edit another configuration file, should

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi Simon, Sorry, we don't have any information on our Wiki. Ceilosca leverages the Ceilometer data collection pipeline via a Ceilometer-Monasca Publisher and the Ceilometer API via a Ceilometer-Monasca Storage Driver and is completely compatible with the Ceilometer v2 API. Regards --Roland Fr

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

Sean Dague wrote on 07/23/2015 01:50:00 PM: > From: Sean Dague > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 07/23/2015 01:50 PM > Subject: Re: [openstack-dev] [openstack][nova] Streamlining of config > options in nova > > [...] > Maybe a directory is fine,

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi Chandeep, There are no fees. It would be great if you could join us. Also, please feel free to add to the agenda topics that you would like to cover. If you are traveling, I can advise on hotels. Regards --Roland From: Chandeep Khamba mailto:ckha...@cray.com>> Reply-To: OpenStack List mail

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Deploy nova-compute (VCDriver) feature

Hi Andrian, this is High priority blueprint [1] for 7.0 timeframe. It seems we still didn't merge the main part [2], and need FF exception for additional stuff. The question is about quality. If we focus on enhancements, then we don't focus on bugs. Which whether means to deliver work with lower q

[openstack-dev] [fuel] [FFE] FF Exception request for Deploy nova-compute (VCDriver) feature

Hi, The patch patch for fuel-library that implements 'compute-vwmare' role ( https://mirantis.jira.com/browse/PROD-627) requires additional work to do (ceilometer support.), but as far as I can see it doesn't affect any other parts of the product. We pl

[openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi, Is the schedule for this meetup confirmed . https://etherpad.openstack.org/p/monasca_liberty_mid_cycle I would like to know if there is any fees involved to join in , or I could just come in . Thanks CHandeep __ OpenSt

[openstack-dev] [Fuel] Switching keystone to apache wsgi

Hi, guys, we're about to switch keystone to apache wsgi by merging [0]. Just wanted to make sure everyone is aware of this change. If you have any questions or concerns let's discuss them in this thread. Regards, Alex [0] https://review.openstack.org/#/c/204111/ _

Re: [openstack-dev] [Ironic] [Oslo] Question about Futurist executors

An example/poc that adds a basic rejection mechanism to various executors (the process pool excecutor internals are complicated and doesn't implement it for that). https://review.openstack.org/205262 With that the following (or similar) could be done: http://paste.openstack.org/show/404591/

Re: [openstack-dev] [requirements][all] stop merging requirements changes

On 24 July 2015 at 05:02, Doug Hellmann wrote: > Because of a faulty test, we've been merging some bad requirements > changes. Please do not approve any more changes until the fixes for the > tests have been merged: > > https://review.openstack.org/#/c/204181 > https://review.openstack.org/#/c/204

Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron

From: Antoni Segura Puimedon mailto:toni+openstac...@midokura.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Thursday, July 23, 2015 at 11:16 AM To: Mohammad Banikazemi mailto:m...@us.ibm.com>>, "Steven Dake (stda

Re: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to Neutron

On Thu, Jul 23, 2015 at 8:10 PM, Stephen Wong wrote: > +1 for Monday > > +1 for Monday UTC. Maybe at 14 or 15h ? > On Wed, Jul 22, 2015 at 10:29 PM, Mohammad Banikazemi > wrote: > >> Gal, This time conflicts with the Neutron ML2 weekly meeting time [1]. I >> realize there are several networkin

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

On Thu, 2015-07-23 at 13:50 -0500, Sean Dague wrote: > Maybe a directory is fine, especially if module mapped to [subsection]. > > nova/config/ >default.py >glance.py >... > > which makes it reasonably discoverable and mappable back and forth from > config file to files. I like that

Re: [openstack-dev] [Fuel] FFE requests and status

Thanks Andrew. I'd like to add that after there is an announcement about FF, all core reviewers should stop getting patches into master which are parts of features or extensions. We expect only bugfixes. If there is anything else, we need to be very transparent about it, and have them in public pl

[openstack-dev] [puppet] Swift_{account, container, object, proxy}_config resources ordering

While implementing my composition module, I've realized that Swift_${type}_config resources should be applied AFTER Concat['/etc/swift/${type}-server.conf'], otherwise the content defined in the resource is overwritten by concat::fragment template. It's my first time contributing and I still have

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Custom node attributes feature

Mike, thanks for the important points you've provided. My main argument for this FFE is the following: we've already got a confirmation from SME for this patch. But also got some not critical comments at the last minute before we were going to merge it and have to handle it now. But it looks that

Re: [openstack-dev] [fuel] Meeting 7/23

I'd like to say a few comments about topics which we didn't have time for: > * ubuntu based bootstrap has been merged, needs thorough testing (kozhukalov) great work, thanks Alexei Sheplyakov for working days and nights to get this done. Thanks kozhukalov for helping him out and getting it into mas

[openstack-dev] [Fuel] FFE requests and status

In case you missed it, feature freeze is today and in the rush to merge things, you may have had issues with getting everything landed. For those that are not familiar with the process, to request a feature freeze exception (FFE): * You will need to raise the request to the ML here and in such me

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

On 07/23/2015 01:04 PM, Kevin L. Mitchell wrote: > On Thu, 2015-07-23 at 11:41 -0500, Sean Dague wrote: >> On 07/23/2015 11:23 AM, Roman Podoliaka wrote: >>> Hi all, >>> >>> FWIW, this is exactly what we have in oslo libs, e.g. in oslo.db [0] >>> >>> Putting all Nova options into one big file is pr

Re: [openstack-dev] Fwd: [MOS] [fuel-library] [keystone] [FFE] FF Exception request for Fernet tokens support.

That's my fault, I asked him to send it as I thought it also required review for FFE. On Jul 23, 2015 1:45 PM, "Mike Scherbakov" wrote: > Alexander, > as this is purely Fuel related thing, please send a new one with right > subject. It has to be [fuel] in subject, and that's it. No MOS, > fuel-li

[openstack-dev] [fuel] FF Exception request for Fernet tokens support.

Colleagues, I would like to request an exception from the Feature Freeze for Fernet tokens support added to the fuel-library in the following CR: https://review.openstack.org/#/c/201029/ Keystone part of the feature is implemented in the upstream and the change impacts setup configuration only.

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

+1 On Thu, Jul 23, 2015 at 10:50 AM Evgeniy L wrote: > +1 > > On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov > wrote: > >> At the moment we have several core reviewers for the fuel-main project. >> >> Roman Vyalov is responsible for merging of infrastructure-related >> variables and for the lis

Re: [openstack-dev] [Neutron][L3] Representing a networks connected by routers

>We ran in to this long ago. What are some other examples? We've be good about keeping the network L2 only. Segments, VLAN transparency, and other properties of the network are all L2. The example you gave about needing the network to see the grouping of subnets isn't the network leaking into L3,

[openstack-dev] [Neutron][SFC] Wiki update - deleting old SFC API

As a courtesy to anyone who may have worked on it, I wanted to notify the list that I'm going to delete [1] from wiki page [2]. I may actually delete [2] completely. I'm going to update the content on [3] to reference the new SFC API spec that has just been merged. Currently [3] links to [2] wh

Re: [openstack-dev] Fwd: [MOS] [fuel-library] [keystone] [FFE] FF Exception request for Fernet tokens support.

Alexander, as this is purely Fuel related thing, please send a new one with right subject. It has to be [fuel] in subject, and that's it. No MOS, fuel-library, FFE please, we don't use any of those tags. No need to spam Keystone team too, as it's configuration related to Fuel only at this point of

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Custom node attributes feature

-1 My concerns are the following: 1. This feature is of a High priority, not Essential [1] 2. We already had to give exception for flexible networking CLI part [2], as it is essential one. So basically that means we have a conflict of focus for SMEs in the area. 3. Just by working o

Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron

This is great news! I can see our two projects working close together since we have aligned but not entirely overlapping goals. Antoni, please reach out on IRC at any time. #kolla is active almost 24/7 due to all of our different timezones. There is usually two cores talking at any given time. I w

Re: [openstack-dev] [kolla][magnum] Removal of Daneyon Hansen from the Core Reviewer team for Kolla

Agreed, everyone should do what they love - so I wish you the best of luck with the Magnum crew Daneyon! Op 22-07-15 om 22:47 schreef Steven Dake (stdake): Fellow Kolla developers, Daneyon has been instrumental in getting Kolla rolling and keeping our project alive. He even found me a new jo

Re: [openstack-dev] [fuel] Meeting 7/23

Yep, forgot to include the topics i referred to Topics not covered in todays meeting, but requested in the agenda * ubuntu based bootstrap has been merged, needs thorough testing (kozhukalov) * Let's switch keystone under Apache right after FF (adidenko) * Separate services from controller status

Re: [openstack-dev] [fuel] FF Exception request for Templates for Networking feature

Looks like the only CLI part left: https://review.openstack.org/#/c/204321/, and you guys did a great job finishing the other two. Looks like we'd need to give FF exception, as this is essential feature. It's glad that we merged all other thousands lines of code. This is the most complex feature,

Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron

On Thu, Jul 23, 2015 at 7:35 PM, Mohammad Banikazemi wrote: > I let the creators of the project speak for themselves but here is my take > on project Kuryr. > > The goal is not to containerize Neutron or other OpenStack services. The > main objective is to use Neutron as a networking backend opti

Re: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to Neutron

+1 for Monday On Wed, Jul 22, 2015 at 10:29 PM, Mohammad Banikazemi wrote: > Gal, This time conflicts with the Neutron ML2 weekly meeting time [1]. I > realize there are several networking related weekly meetings, but I would > like to see if we can find a different time. I suggest the same time

[openstack-dev] [fuel] Meeting 7/23

Today's meeting was a little hectic, if you have a topic on the agenda, ensure you are present and ready to speak, or move your topic lower in the agenda. When possible, pre-type you main points of discussion and copy and paste it into the channel when your topic comes up. This tends to save a bit

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Env Upgrade feature

Oleg, considering that your feature is essential for the release, sounds like there is no way we can't give an exception. I'm glad that it's perceived by low risk by core reviewer from Nailgun team (Evgeny). If there are no concerns from other, then we are giving FF exception. However, I'd like to

Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron

For my low-orbit perspective (I would have lied if I said 10,000 or 30,000 ft!) Kuryr's ultimate goal is to provide: 1) a container-oriented set of neutron plugins and drivers (you know the ML2 driver, a l3 svc plugin, a lbaas driver, etc. etc.) 2) possibly (I'm not sure if that's the case) control

Re: [openstack-dev] [cross-project] "Admin" ness not properly scoped

On 07/23/2015 01:11 PM, melanie witt wrote: On Jul 23, 2015, at 7:35, Adam Young wrote: What this means is the if a user is assigned "admin" on any project, they are assigned admin for everything. Fixing this is going to require a change to how we write policy. Each policy rule needs to hav

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

On Thu, 2015-07-23 at 11:41 -0500, Sean Dague wrote: > On 07/23/2015 11:23 AM, Roman Podoliaka wrote: > > Hi all, > > > > FWIW, this is exactly what we have in oslo libs, e.g. in oslo.db [0] > > > > Putting all Nova options into one big file is probably not a good > > idea, still we could conside

Re: [openstack-dev] [keystone] token revocation woes

Morgan asked me to post some of my numbers here. From my staging environment: With 0 revocations: Requests per second:104.67 [#/sec] (mean) Time per request: 191.071 [ms] (mean) With 500 revocations: Requests per second:52.48 [#/sec] (mean) Time per request: 381.103 [ms] (mean

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Env Upgrade feature

Hi, The patch into Nailgun requires additional work to do, but as far as I can see it doesn't affect any other parts of the system, also it's implemented as an extension, which means if the feature will introduce bugs which we won't be able to fix in a required time, it can be easily disabled with

Re: [openstack-dev] [Fuel][python-fuelclient] Implementing new commands

2015-07-23 18:28 GMT+02:00 Stanislaw Bogatkin : > Hi, > > can we just add all needed functionality from old fuel client that fuel2 > needs, then say that old fuel-client is deprecated now and will not support > some new features, then add new features to fuel2 only? It seems like best > way for me

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Custom node attributes feature

+1 for this FFE as it's important to have this functionality covered in CLI 2015-07-23 19:46 GMT+02:00 Igor Kalnitsky : > Hi Julia, > > I'm ok with FF exception for CLI part. I don't think it can somehow > decrease product quality, so as a core I'll help to land it. > > Thanks, > Igor > > On Thu,

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

+1 On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov wrote: > At the moment we have several core reviewers for the fuel-main project. > > Roman Vyalov is responsible for merging of infrastructure-related > variables and for the lists of packages. > I am responsible for merges in make system. And I

[openstack-dev] Fwd: [MOS] [fuel-library] [keystone] [FFE] FF Exception request for Fernet tokens support.

-- Forwarded message -- From: Alexander Makarov Date: Thu, Jul 23, 2015 at 5:30 PM Subject: [MOS] [fuel-library] [keystone] [FFE] FF Exception request for Fernet tokens support. To: Vitaly Sedelnik , Eugene Bogdanov < ebogda...@mirantis.com>, Igor Marnat , Ilya Elterman < ielter...

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Custom node attributes feature

Hi Julia, I'm ok with FF exception for CLI part. I don't think it can somehow decrease product quality, so as a core I'll help to land it. Thanks, Igor On Thu, Jul 23, 2015 at 7:50 PM, Julia Aranovich wrote: > Team, > > I would like to request an exception from the Feature Freeze for CLI change

Re: [openstack-dev] [horizon] Minimum Unit Test Coverage

I was referring to the HTML reports that the karma-coverage plugin creates for now. From my experience with it, it’s fairly relaxed about what counts as something being tested, hence the 100% aim. For example, often just checking that a value is defined is enough for it to be “tested”, and this

Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron

I let the creators of the project speak for themselves but here is my take on project Kuryr. The goal is not to containerize Neutron or other OpenStack services. The main objective is to use Neutron as a networking backend option for Docker. The original proposal was to do so in the context of usi

Re: [openstack-dev] [Fuel] Get rid of fuelmenu

I'm against getting rid of fuelmenu. As Alex wrote - we need to remember who are the people that we are targeting. We are adding multiple dialog windows with confirmations, warnings and special way to do dangerous actions (like environment deletion or reset), but in the same time we want to force u

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

+1 2015-07-23 19:23 GMT+02:00 Dmitry Borodaenko : > +1 > > On Thu, Jul 23, 2015, 09:32 Stanislaw Bogatkin > wrote: > >> +1 >> >> On Thu, Jul 23, 2015 at 10:43 AM, Roman Vyalov >> wrote: >> >>> +1 >>> >>> On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov >>> wrote: >>> At the moment we have s

Re: [openstack-dev] [keystone] token revocation woes

On 07/23/2015 10:45 AM, Lance Bragstad wrote: On Wed, Jul 22, 2015 at 10:06 PM, Adam Young > wrote: On 07/22/2015 05:39 PM, Adam Young wrote: On 07/22/2015 03:41 PM, Morgan Fainberg wrote: This is an indicator that the bottleneck is not the db strictly

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

+1 On Thu, Jul 23, 2015, 09:32 Stanislaw Bogatkin wrote: > +1 > > On Thu, Jul 23, 2015 at 10:43 AM, Roman Vyalov > wrote: > >> +1 >> >> On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov >> wrote: >> >>> At the moment we have several core reviewers for the fuel-main project. >>> >>> Roman Vyalov i

  1   2   >