Re: [openstack-dev] [tripleo] Pin some puppet dependencies on git clone

On 15.12.2015 17:46, Emilien Macchi wrote: For information, Puppet OpenStack CI is consistent for unit & functional tests, we use a single (versionned) Puppetfile: https://github.com/openstack/puppet-openstack-integration/blob/master/Puppetfile TripleO folks might want to have a look at this to

Re: [openstack-dev] [oslo] stable/liberty branch needed for oslo-incubator

On 12/13/2015 10:33 PM, Robert Collins wrote: On 14 December 2015 at 15:28, Matt Riedemann wrote: I don't have a pressing need to backport something right now, but as long as there was code in oslo-incubator that *could* be synced to other projects which wasn't

Re: [openstack-dev] [tripleo] Pin some puppet dependencies on git clone

For information, Puppet OpenStack CI is consistent for unit & functional tests, we use a single (versionned) Puppetfile: https://github.com/openstack/puppet-openstack-integration/blob/master/Puppetfile TripleO folks might want to have a look at this to follow the dependencies actually supported

Re: [openstack-dev] [Cinder] Rolling upgrades

On Tue, Dec 15, 2015 at 01:09:10PM +0100, Micha?? Dulko wrote: > Hi, > > At the meeting recently it was mentioned that our rolling upgrades > efforts are pursuing an "elusive unicorn" that makes development a lot > more complicated and restricted. I want to try to clarify this a bit, > explain

Re: [openstack-dev] [cinder] Custom fields for versioned objects

On Tue, Dec 15, 2015 at 04:46:02PM +0100, Micha?? Dulko wrote: > On 12/15/2015 04:08 PM, Ryan Rossiter wrote: > > Thanks for the review Michal! As for the bp/bug report, there???s four > > options: > > > > 1. Tack the work on as part of bp cinder-objects > > 2. Make a new blueprint (bp

Re: [openstack-dev] [tripleo] Pin some puppet dependencies on git clone

I suggest then to pin the dependencies from [1] to below. Couldn't be posible to just clone the openstack/puppet-* ones and then use some tool to install the dependencies from them, some kind of pip install -r requirements.txt but adapted for Puppet? Does this tool exist? [1]:

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

My $0.02: heat as it is today, requires all users to be devops, and to carefully craft the templates launched specific to the cloud and the particular app they are trying to write. Making sharing code between heat users difficult. This means the potential user base of heat is restricted to

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

Hi Ihar, wow, good job!! Sorry for the very slow reply. I really like your proposal...some comments inline. On 12/03/2015 04:46 PM, Ihar Hrachyshka wrote: Hi, Small update on the RFE. It was approved for Mitaka, assuming we come up with proper details upfront thru neutron-specs process. In

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Kyle Mestery wrote: >> o) Workaround: >> >> After a vm is deployed on a (re)started compute node, restart taas >> agent before creating a tap-service or tap-flow. >> That is, create taas flows after cleanup has been done. >> >> Note that cleanup will

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hey Mike, Thanks for your input. > actually not. if you replace your ARRAY columns with JSON entirely, It still needs to fix the code, i.e. change ARRAY-specific queries with JSON ones around the code. ;) > there's already a mostly finished PR for SQLAlchemy support in the queue. Does it

Re: [openstack-dev] [Fuel][Ubuntu bootstrap] WebUI notification

Hi, I really don't like setting the error message as the default one in the DB schema and consider it as a last resort solution. If possible update the message to error one just before you start to build the image. 2015-12-15 18:48 GMT+03:00 Artur Svechnikov : > Hi

[openstack-dev] [neutron] neutron-lib subteam

Hi all, We are starting a formal neutron-lib subteam for work revolving around neutron-lib and general decoupling efforts of all neutron projects. The first meeting is tomorrow at 1730 UTC in #openstack-meeting-4. More info can be found here:

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

Excerpts from Fox, Kevin M's message of 2015-12-15 09:07:02 -0800: > My $0.02: > > heat as it is today, requires all users to be devops, and to carefully craft > the templates launched specific to the cloud and the particular app they are > trying to write. Making sharing code between heat

Re: [openstack-dev] [Fuel] Different versions for different components

Aleksandra, thank you for the clarification, it makes sense to me now. In my opinion our current approach is not flexible at all and very outdated. After splitting fuel-web to smaller components we realized that some of them may be actually used outside of a master node as standalone things.

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Folks, I want to bring this up again. There were no progress since last Oleg's mail, and we must decide. It's good that we still have "2015.1.0-8.0" version while OpenStack uses "Liberty" name for versions. Let's decide which name to use, file a bug and finally resolve it. - Igor On Thu, Oct

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Assaf Muller wrote: SFC are going to hit this issue as well. Really any out of tree Neutron project that extends the OVS agent and expects things to work :) Yes. SFC project is considered for l2 agent extensions mechanism, though we need to deliver in core first. AFAIK

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Vilobh, Thanks for advancing this important topic. I took a look at what Tim referenced how Nova is implementing nested quotas, and it seems to me that’s something we could fold in as well to our design. Do you agree? Adrian On Dec 14, 2015, at 10:22 PM, Tim Bell

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Thanks… it is really important from the user experience that we keep the nested quota implementations in sync so we don’t have different semantics. Tim From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: 15 December 2015 18:44 To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

+1 to Igor suggestion to downgrade Postgres to 9.2. Our users don't work directly with Postgres, so there is no any deprecation of Fuel features. Maintaining our own custom Postgres package just because we want "JSON column" is not a rational decision. Come on, fuel is not a billing system with

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

+1 to Vova and Sasha, I voted for 9.2 at the beginning of the thread due to potential packaging and infrastructure issues, but since Artem and Sasha insist on 9.3, I see no reasons to keep 9.2. 2015-12-15 22:19 GMT+03:00 Aleksandra Fedorova : > Igor, > > that's an

Re: [openstack-dev] [oslo][oslo.log]

IMHO, go for it, the yaml should probably be of the format that the following uses so that it's easily known what the format actually is: https://docs.python.org/2/library/logging.config.html#logging.config.dictConfig So convert yaml -> that dict format -> profit! -Josh Vladislav Kuzmin

[openstack-dev] [Fuel] Proposal to Delay Docker Removal From Fuel Master Node

Folks This email is a proposal to push Docker containers removal from the master node to the date beyond 8.0 HCF. Here is why I propose to do so. Removal of Docker is a rather invasive change and may introduce a lot of regressions. It is well may affect how bugs are fixed - we might have 2 ways

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Folks Let me add my 2c here. I am for using Postgres 9.3. Here is an additional argument to the ones provided by Artem, Aleksandra and others. Fuel is being sometimes highly customized by our users for their specific needs. It has been Postgres 9.3 for a while and they might have as well gotten

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

IMHO for Magnum and Nested Quota we need more discussion before proceeding ahead because :- 1. The main intent of hierarchical multi tenancy is creating a hierarchy of projects (so that its easier for the cloud provider to manage different projects) and nested quota driver being able to validate

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Vilobh/Tim, could you elaborate about your use-cases around Magnum quota? My concern is that user will be easy lost in quotas ;). e.g. we already have nova/cinder/neutron and Kub/Mesos(Framework) quotas. There are two use-cases: - tenant has it’s own list of bays/clusters (nova/cinder/neutron

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Igor, that's an anonymous vote for question stated in a wrong way. Sorry, but it doesn't really look like a valuable input for the discussion. On Tue, Dec 15, 2015 at 9:47 PM, Igor Kalnitsky wrote: > FYI: so far (according to poll [1]) we have > > * 11 votes for keeping

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Igor Sorry, this vote is irrelevant as it is not about all the concerns rasied by Artem, Aleksandra and me. It is about JSON vs non-JSON Postgres which is not exactly the case. On Tue, Dec 15, 2015 at 9:47 PM, Igor Kalnitsky wrote: > FYI: so far (according to poll [1])

Re: [openstack-dev] [tripleo] Pin some puppet dependencies on git clone

On 12/15/2015 12:23 PM, Jiří Stránský wrote: > On 15.12.2015 17:46, Emilien Macchi wrote: >> For information, Puppet OpenStack CI is consistent for unit & functional >> tests, we use a single (versionned) Puppetfile: >>

Re: [openstack-dev] [Fuel] Proposal to Delay Docker Removal From Fuel Master Node

+1 Regards, Andrey Maximov Fuel Project Manager On Tue, Dec 15, 2015 at 9:41 PM, Vladimir Kuklin wrote: > Folks > > This email is a proposal to push Docker containers removal from the master > node to the date beyond 8.0 HCF. > > Here is why I propose to do so. > >

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Hi folks, I would propose to keep current versioning schema until fuel release schedule is fully aligned with OpenStack releases. AFAIK it is expected to happen since 9.0. After it we can switch to OpenStack version names. BR, Dmitry. On Tue, Dec 15, 2015 at 8:41 PM, Igor Kalnitsky

Re: [openstack-dev] [Sender Auth Failure] Re: [neutron] How could an L2 agent extension access agent methods ?

Hello Ihar, I have some comments and questions about your proposal. My apologies if any of what I say here results from misunderstandings on my part. 1. I believe there are two sorts of redirection at play here. The first involves inter-table traversal while the second allows a frame to exit

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

FYI: so far (according to poll [1]) we have * 11 votes for keeping 9.2 * 4 votes for restoring 9.3 [1] https://docs.google.com/spreadsheets/d/1RNcEVFsg7GdHIXlJl-6LCELhlwQ_zmTbd40Bk_jH1m4/edit?usp=sharing On Tue, Dec 15, 2015 at 8:34 PM, Vladimir Kuklin wrote: > Folks > >

Re: [openstack-dev] [midonet] Split up python-midonetclient

No. I'm saying that I prefer python-os-midonetclient to be a project by its own instead of being merged inside the neutron plugin repo. On 14 December 2015 at 18:43, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > > > On Mon, Dec 14, 2015 at 6:07 PM, Jaume Devesa

[openstack-dev] [Fuel] [Plugins] Ways to improve plugin links handling in 9.0

Hi, As you may know, in Fuel 8.0 we've implemented blueprint external-dashboard-links-in-fuel-dashboard . It will allow plugins to add links to their dashboards to the Fuel UI after deployment. As link

Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race conditions)?

On 12/15/2015 03:33 AM, Cheng, Yingxin wrote: > >> -Original Message- >> From: Nikola Đipanov [mailto:ndipa...@redhat.com] >> Sent: Monday, December 14, 2015 11:11 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [nova] Better tests

Re: [openstack-dev] [Fuel] Nominate Bulat Gaifulin for fuel-web & fuel-mirror cores

+1 On Mon, Dec 14, 2015 at 3:20 PM, Roman Vyalov wrote: > +1 > > On Mon, Dec 14, 2015 at 3:05 PM, Aleksey Kasatkin > wrote: > >> +1. >> >> >> Aleksey Kasatkin >> >> >> On Mon, Dec 14, 2015 at 12:49 PM, Vladimir Sharshov < >> vshars...@mirantis.com>

Re: [openstack-dev] [Fuel] Nominate Bulat Gaifulin for fuel-web & fuel-mirror cores

+1 On Tue, Dec 15, 2015 at 12:33 PM, Anastasia Urlapova wrote: > +1 > > On Mon, Dec 14, 2015 at 3:20 PM, Roman Vyalov > wrote: > >> +1 >> >> On Mon, Dec 14, 2015 at 3:05 PM, Aleksey Kasatkin > > wrote: >> >>> +1. >>> >>>

Re: [openstack-dev] [Neutron] Team meeting this Tuesday at 1400UTC

I want to quickly share the status on the modular l2 agent (common agent) refactoring blueprint [1] - I'm not able to attend this afternoon... - Till Christmas, I would like to see the extension manager patchset merged [2] - The goal for Mitaka-2 is to make the split between the common part and

Re: [openstack-dev] [cinder] Custom fields for versioned objects

On 12/14/2015 03:59 PM, Ryan Rossiter wrote: > Hi everyone, > > I have a change submitted that lays the groundwork for using custom enums and > fields that are used by versioned objects [1]. These custom fields allow for > verification on a set of valid values, which prevents the field from

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

On Mon, Dec 14 2015, Igor Kalnitsky wrote: > The things I want to notice are: > > * Currently we aren't tied up to PostgreSQL 9.3. > * There's a patch [2] that ties Fuel up to PostgreSQL 9.3+ by using a > set of JSON operations. I'm curious and have just a small side question: does that mean

Re: [openstack-dev] [Fuel] [Plugins] Ways to improve plugin links handling in 9.0

Igor, 2015-12-15 13:14 GMT+03:00 Igor Kalnitsky : > Hey Vitaly, > > I agree that having a lot of logic (receiving auth token, creating > payload and doing post request) in RPM post_install section is a huge > overhead, and definitely it's not a way to go. We have to find

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hey Julien, > https://blueprints.launchpad.net/fuel/+spec/openstack-ha-fuel-postgresql I believe this blueprint is about DB for OpenStack cloud (we use Galera now), while here we're talking about DB backend for Fuel itself. Fuel has a separate node (so called Fuel Master) and we use PostgreSQL

Re: [openstack-dev] [Fuel] [Plugins] Ways to improve plugin links handling in 9.0

Hey Vitaly, I agree that having a lot of logic (receiving auth token, creating payload and doing post request) in RPM post_install section is a huge overhead, and definitely it's not a way to go. We have to find better solution, and I think it should be done declaratively (via some YAML).

[openstack-dev] [Fuel] Different versions for different components

Folks, I can see that version for python-fuelclient package is already [1] set to 8.0.0. However, there’s still no corresponding tag and so the version was not released to PyPi. The question is it finally safe to tag different versions for different components? As for Fuel client we need to

Re: [openstack-dev] [Neutron] Team meeting this Tuesday at 1400UTC

On 14/12/15 20:37, Armando M. wrote: > Hi neutrinos, > > A kind reminder for this week's meeting. > > For this week we'll continue with the post-milestone format: we'll > continue talking about blueprints/specs and RFEs. We'll be brief on > announcements and bugs, and skip the other sections, docs

[openstack-dev] [Cinder] Rolling upgrades

Hi, At the meeting recently it was mentioned that our rolling upgrades efforts are pursuing an "elusive unicorn" that makes development a lot more complicated and restricted. I want to try to clarify this a bit, explain the strategy more and give an update on the status of the whole affair. So

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hello! I got another few points against downgrading. 1. PostgreSQL-9.2 will reach end-of-life at September 2017 according to [0]. With high probability it means that we will have 9.2 version in centos repos when fuel9.0 arrives. It means that we will have to repackage it anyway just later a

Re: [openstack-dev] [midonet] Split up python-midonetclient

Just leave it as is. This whole thread is a waste of time. On Dec 15, 2015 18:52, "Jaume Devesa" wrote: > No. I'm saying that I prefer python-os-midonetclient to be a project by > its own > instead of being merged inside the neutron plugin repo. > > On 14 December 2015 at

Re: [openstack-dev] [Fuel] Different versions for different components

Roman, we use 8.0 version everywhere in Fuel code _before_ 8.0 release. We don't use bump approach, rather bump version, run a development and test cycle, then create release and tag it. In more details: 1) there is a master branch, in which development for upcoming release (currently 8.0)

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

Clark, What about ephemeral storage at OVH vms? I see may storage related errors (see full output below) these days. Basically it means Docker cannot create storage device at local drive -- Logs begin at Mon 2015-12-14 06:40:09 UTC, end at Mon 2015-12-14 07:00:38 UTC. -- Dec 14 06:45:50

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hello, I made an attempt to gather all valuable points 'for' and 'against' 9.2.x in one document [1]. Please take a look on it, I also put some comments there to keep everything in one place. I believe this can help us to make deliberated decision. Please add more pros / cons there as I don't

Re: [openstack-dev] [astara][requirements] astara-appliance has requirements not in global-requirements

Thanks for the heads up, Andreas. I've opened https://bugs.launchpad.net/astara/+bug/1526527 and hope to resolve it in the coming days. Cheers Adam On Sun, Dec 13, 2015 at 3:26 AM, Andreas Jaeger wrote: > Astara team, > > The requirements proposal job complains about

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

There is no ephemeral drive you will have to use the root disk. Grabbing a random VM in OVH and running a quick df on it you should have about 60GB of free space for the job to use there. Clark On Tue, Dec 15, 2015, at 02:00 PM, Egor Guz wrote: > Clark, > > > What about ephemeral storage at

Re: [openstack-dev] [Neutron] Team meeting this Tuesday at 1400UTC

On 15 December 2015 at 04:22, Neil Jerram wrote: > On 14/12/15 20:37, Armando M. wrote: > > Hi neutrinos, > > > > A kind reminder for this week's meeting. > > > > For this week we'll continue with the post-milestone format: we'll > > continue talking about

[openstack-dev] [OSSN 0061] Glance image signature uses an insecure hash algorithm (MD5)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Glance image signature uses an insecure hash algorithm (MD5) - --- ### Summary ### During the Liberty release the Glance project added a feature that supports verifying images by their signature. There is a flaw in the implementation that degrades

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

On Sun, Dec 13, 2015, at 10:51 AM, Clark Boylan wrote: > On Sat, Dec 12, 2015, at 02:16 PM, Hongbin Lu wrote: > > Hi, > > > > As Kai Qiang mentioned, magnum gate recently had a bunch of random > > failures, which occurred on creating a nova instance with 2G of RAM. > > According to the error

[openstack-dev] [searchlight] Weekly IRC meeting cancelled December 17th & 24th

We will not be holding our weekly IRC meeting this week due to the busy holiday season with many people out. Our regular meeting will resume Thursday, December 31st. As always, you can find the meeting schedule and agenda here: http://eavesdrop.openstack.org/#Searchlight_Team_Meeting Thanks,

Re: [openstack-dev] [Neutron][Tricircle]The process for adding networking-tricircle

Hi, Ihar, Is there any sub-project under Neutron stadium dealing with cross Neutron L2/L3 networking? If there is no one, why not introduce a new one. More information about what the plugin wants to do:

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

Thanks Clark and infra guys to work around that. We would keep track that and see if such issue disappear. Thanks Best Wishes, Kai Qiang Wu (吴开强 Kennan） IBM China System and Technology Lab, Beijing E-mail:

[openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hello folks, This topic is about configuration storage which will connect data sources (nailgun/bareon/others) and orchestration. And right now we are developing two projects that will overlap a bit. I understand there is not enough context to dive into this thread right away, but i will

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Dmitry, Thank you for this document! Please move it on https://etherpad.openstack.org to make it accessible Best regards, Alexey Shtokolov 2015-12-16 1:38 GMT+03:00 Dmitry Teselkin : > Hello, > > I made an attempt to gather all valuable points 'for' and 'against' >

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

o) An idea to fix: 1. Set "taas" stamp(*) to taas flows. 2. Modify the cleanup logic in ovs-agent not to delete entries stamped as "taas". * Maybe a static string. If we need to use a string which generated dynamically (e.g. uuid), API to interact

Re: [openstack-dev] [cinder] Custom fields for versioned objects

On 12/15/2015 04:08 PM, Ryan Rossiter wrote: > Thanks for the review Michal! As for the bp/bug report, there’s four options: > > 1. Tack the work on as part of bp cinder-objects > 2. Make a new blueprint (bp cinder—object-fields) > 3. Open a bug to handle all changes for enums/fields > 4. Open a

Re: [openstack-dev] [TripleO] RFC: profile matching

On 11/09/2015 03:51 PM, Dmitry Tantsur wrote: Hi folks! I spent some time thinking about bringing profile matching back in, so I'd like to get your comments on the following near-future plan. First, the scope of the problem. What we do is essentially kind of capability discovery. We'll help

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

Hi Sergey, I agree with your feeling, this is from the Heat Wiki page. "Heat also endeavours to provide compatibility with the AWS CloudFormation template format, so that many existing CloudFormation templates can be launched on OpenStack." Note also, there was another review that attempted

[openstack-dev] [Fuel][Ubuntu bootstrap] WebUI notification

Hi folks, Recently was introduced special notification about absented bootstrap image. Currently this notification is sent from fuel-bootstrap-cli. It means that error message will not be sent when failure occurs before first building (like in [1]). I think it will be better to set error message

[openstack-dev] [OSSN 0062] Potential reuse of revoked Identity tokens

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Potential reuse of revoked Identity tokens - --- ### Summary ### An authorization token issued by the Identity service can be revoked, which is designed to immediately make that token invalid for future use. When the PKI or PKIZ token providers are

Re: [openstack-dev] Regarding Designate install through Openstack-Ansible

Hi Major, Jean, Jesse and Kevin, I have added some part of Designate code and uploaded it on https://github.com/sharmaswati6/designate_files Could you please review this and help me in answering the following questions- Is there some specific location for the server-side code for all Openstack

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

hi, On Fri, Dec 4, 2015 at 12:46 AM, Ihar Hrachyshka wrote: > Hi, > > Small update on the RFE. It was approved for Mitaka, assuming we come up > with proper details upfront thru neutron-specs process. > > In the meantime, we have found more use cases for flow management

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

I'd support PostgreSQL 9.3 in 8.0. * It is clear that PostgreSQL downgrade wasn't planned and discussed before Feature Freeze, so this change is accidental. We didn't investigate all possible consequences and changes required for the switch. * In Infra we have all our unit tests run on PostgreSQL

Re: [openstack-dev] [nova] Microversions support for extensions without Controller

Hi, Alexandre, we discussed this on api meeting http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-12-15-12.00.log.html Finally people agreement on merge os-user-data into servers. I will submit a patch up for this merge. Thanks Alex 2015-12-14 21:24 GMT+08:00 Alex Xu

[openstack-dev] [oslo][oslo.log]

Hi, I want to specify all my option in yaml file, because it is much more readable. But I must use ini file, because oslo.log using logging.config.fileConfig for reading the config file ( https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L216) Why we cannot use yaml file? Can I

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Artem - > PostgreSQL-9.2 will reach end-of-life at September 2017 according to [0]. Python 2.7 will reach end-of-life at the beginning of 2020. However, we don't drop Python 2.7 and don't start using Python 3.5 instead. Moreover we aren't going to have CentOS 7 forever. I believe either new

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

I have a few changes in review [0] that implement a plan outlined in the bug [1] for seamless merge of the new versioning schema (liberty-8.0). With those changes merged in order, we should be OK without changing ISO in Fuel infra. I also have version of ISO with green BVT that incorporates

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

Hi! Can I offer a counter point? Quotas are for _real_ resources. Memory, CPU, disk, bandwidth. These are all _closely_ tied to things that cost real money and cannot be conjured from thin air. As such, the user being able to allocate 1 billion or 2 containers is not limited by Magnum, but by

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

On Tue, Dec 15, 2015 at 9:47 PM, Igor Kalnitsky wrote: > * 11 votes for keeping 9.2 > * 4 votes for restoring 9.3 Igor, please remove my vote from "9.2", I voted for "I'm too conservative, I want to see classic RDBMS approach" , but not to keep accidentally downgraded

Re: [openstack-dev] [Neutron][Tricircle]The process for adding networking-tricircle

Zhipeng Huang wrote: Hi Neutrinos, We the Tricircle team want to have a neutron-ovn like agent in Neutron for our networking management. Before we go into discussing tech details on how new subprojects are introduced, let me ask one question: have you actually

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Soichi Shigeta wrote: Hi, We find a problem that neutron ovs-agent deletes taas flows. o) Problem description: Background: At Liberty, a bug fix to drop only old flows was merged to Neutron. When ovs-agent is restarted, the cleanup

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

> getting rid of the raciness of ClusteredComputeManager in my >current deployment. And I'm willing to help other operators do the same. You do alleviate race, but at the cost of complexity and unpredictability. Breaking that down, let's say we go with the current plan and the compute host

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

the one thing as an Op I'd like to see avoided is having the template language be Turing complete. When I'm provisioning heat-engines its much easier if you know how many you need when the user can't force them to spin in an infinite loop or other such nasties. I think jinja maybe manages to do

Re: [openstack-dev] [Sender Auth Failure] Re: [neutron] How could an L2 agent extension access agent methods ?

On Tue, Dec 15, 2015 at 05:58:14PM +, Frances, Margaret wrote: > 2. OpenFlow¹s Goto instruction directs a frame from one table to the next. > A redirection in this sense must be to a higher-numbered table, which is > to say that OF pipeline processing can only go forward (see p.18, para.2 >

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

Excerpts from Fox, Kevin M's message of 2015-12-15 17:21:13 -0800: > the one thing as an Op I'd like to see avoided is having the template > language be Turing complete. When I'm provisioning heat-engines its much > easier if you know how many you need when the user can't force them to spin >

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

Hi AFEK, Sorry I was busy in other things and didn't pay much attention to Vitrage project(But I will do :) ), the notification message I metioned doesn't mean the notification based on "alarm_actions". currently, when a alarm's state changed, it will trigger the alarm actions specified in

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Wow such a hot topic... I'm also the one who voted for 9.2. But I also voted like Alexey S., "I'm conservative..." - I am actually mostly conservative, and would question every new cool tool/feature of library unless there is a very good proof on using it. You can't build a product which will have

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

SFC are going to hit this issue as well. Really any out of tree Neutron project that extends the OVS agent and expects things to work :) On Tue, Dec 15, 2015 at 9:30 AM, Ihar Hrachyshka wrote: > Soichi Shigeta wrote: > >> >> Hi, >> >> We

Re: [openstack-dev] [cinder] Custom fields for versioned objects

Thanks for the review Michal! As for the bp/bug report, there’s four options: 1. Tack the work on as part of bp cinder-objects 2. Make a new blueprint (bp cinder—object-fields) 3. Open a bug to handle all changes for enums/fields 4. Open a bug for each changed enum/field Personally, I’m partial

[openstack-dev] [nova] Reminder: Low Priority Blueprint Review Day is Thursday 17th December 2015

To help with the review push on Thursday, I have created a list of the blueprint reviews, that are approved, have Jenkins passing, and are more than 50 days old. The list is a new section at the top of the regular etherpad we use to track the most important reviews:

Re: [openstack-dev] [puppet] weekly meeting #63

On 12/14/2015 08:55 AM, Emilien Macchi wrote: > Hello! > > Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151215 > > See you there! We did our mee

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

Hello! We use mysql-wsrep-5.6 which is latest for galera. It is based on MySQL-5.6.27. So JSON features here is not available yet. Regards, Artem Silenkov --- MOS-Packaging On Tue, Dec 15, 2015 at 6:06 PM, Mike Bayer wrote: > > > On 12/15/2015 07:20 AM, Igor Kalnitsky

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

On 12/15/2015 07:20 AM, Igor Kalnitsky wrote: > Hey Julien, > >> https://blueprints.launchpad.net/fuel/+spec/openstack-ha-fuel-postgresql > > I believe this blueprint is about DB for OpenStack cloud (we use > Galera now), while here we're talking about DB backend for Fuel > itself. Fuel has a

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

On Tue, Dec 15, 2015 at 9:11 AM, Assaf Muller wrote: > SFC are going to hit this issue as well. Really any out of tree > Neutron project that extends the OVS agent and expects things to work > :) > > Yes, this is the case. > On Tue, Dec 15, 2015 at 9:30 AM, Ihar Hrachyshka

[openstack-dev] [Smaug]Application Data protection as a Service introduction

Hi All, Smaug is a new OpenStack project, aiming at providing a full *Application Data Protection* (e.g DR), including all OpenStack resources. Our Mission Statement: Formalize Application Data Protection in OpenStack (APIs, Services, Plugins, …) Be able to protect Any Resource in OpenStack

Re: [openstack-dev] [nova] Better tests for nova scheduler(esp. race conditions)?

On 15 December 2015 at 10:03, Nikola Đipanov wrote: > On 12/15/2015 03:33 AM, Cheng, Yingxin wrote: >> >>> -Original Message- >>> From: Nikola Đipanov [mailto:ndipa...@redhat.com] >>> Sent: Monday, December 14, 2015 11:11 PM >>> To: OpenStack Development Mailing List

Re: [openstack-dev] [Fuel] Proposal to Delay Docker Removal From Fuel Master Node

+1 Regards, Bulat Gaifullin Mirantis Inc. > On 15 Dec 2015, at 22:19, Andrew Maksimov wrote: > > +1 > > Regards, > Andrey Maximov > Fuel Project Manager > > On Tue, Dec 15, 2015 at 9:41 PM, Vladimir Kuklin >

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Sorry, that I don't see this earlier. Yes, cookies have integer values, so we won't be able to set string there. May be we can have a reserved integer cookie value for a project like all "1". I won't support idea of modifying cleanup logic not to drop 0x0 cookies. During implementation of

[openstack-dev] [tricircle] weekly meeting of Dec.16

Hi, Let’s have regular meeting today starting UTC1300 at #openstack-meeting Agenda: Progress of To-do list: https://etherpad.openstack.org/p/TricircleToDo Discussion of stateless design. Best Regards Chaoyi Huang ( Joe Huang ) From: joehuang [mailto:joehu...@huawei.com] Sent: Tuesday,

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

Excerpts from James Penick's message of 2015-12-15 17:19:19 -0800: > > getting rid of the raciness of ClusteredComputeManager in my > >current deployment. And I'm willing to help other operators do the same. > > You do alleviate race, but at the cost of complexity and > unpredictability.

Re: [openstack-dev] [Fuel] Proposal to Delay Docker Removal From Fuel Master Node

-1 We already discussed this and we have made a decision to move stable branch creation from HCF to SCF. There were reasons for this. We agreed that once stable branch is created, master becomes open for new features. Let's avoid discussing this again. Vladimir Kozhukalov On Wed, Dec 16, 2015