Re: [openstack-dev] [nova] Distributed Database

Excerpts from Jay Pipes's message of 2016-05-02 10:43:21 -0700: > On 05/02/2016 11:51 AM, Mike Bayer wrote: > > On 05/02/2016 07:38 AM, Matthieu Simonin wrote: > >> As far as we understand the idea of an ORM is to hide the relational > >> database with an Object oriented API. > > > > I actually

Re: [openstack-dev] [kolla][gate] Add a gating check job for precheck

does Kolla really need a new job to run the precheck? why not run the precheck before deploying the kolla in the current logical? On Tue, May 3, 2016 at 12:45 PM, Hui Kang wrote: > Steve, > Ok, I created a bp for this. Feel free to edit >

Re: [openstack-dev] [kolla][gate] Add a gating check job for precheck

Steve, Ok, I created a bp for this. Feel free to edit https://blueprints.launchpad.net/kolla/+spec/gate-job-precheck Best regards, - Hui On Mon, May 2, 2016 at 11:50 PM, Steven Dake (stdake) wrote: > Hui, > > I am planning to add a general gating blueprint with work items for

[openstack-dev] [tricircle]cross pod L2 networking update in the design doc

Hello, As the cross pod L2 networking is in review, and after some discussion with guy working in L2GW project, I think we don't need to support DCI SDN Controller for cross pod L2 networking, L2GW will be good to provide different networking options. Therefore the design doc

Re: [openstack-dev] Timeframe for naming the P release?

On 05/02/2016 08:07 PM, Rochelle Grober wrote: But, the original spelling of the landing site is Plimoth Rock. There were still highway signs up in the 70's directing folks to "Plimoth Rock" --Rocky Who should know about rocks ;-) -Original Message- From: Brian Haley

Re: [openstack-dev] [kolla][gate] Add a gating check job for precheck

Hui, I am planning to add a general gating blueprint with work items for the 24 gates we identified. Just g o ahead and get started and I'll have the gate blueprint ready to go by tomorrow. Regards -steve On 5/2/16, 8:41 PM, "Hui Kang" wrote: >Fellow kolla developers,

[openstack-dev] [kolla][gate] Add a gating check job for precheck

Fellow kolla developers, I am wondering if anyone is working on adding a gate job for precheck. If not, I'd like to kick off the task by adding a bp. Any comment? Thanks. - Hui Kang IRC: huikang __ OpenStack Development

Re: [openstack-dev] [Openstack-operators] [OpenStack-Ansible] Mitaka Upgrade

Hi Wade, sorry for the late reply most of us have been traveling / afk for a bit for the summit. Regarding Liberty > Mitaka upgrades there are a few issues that we need to work out before we have a supported upgrade process. Most notably we need to address: *

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Comments inline... On Mon, May 2, 2016 at 7:39 PM, Matt Fischer wrote: > On Mon, May 2, 2016 at 5:26 PM, Clint Byrum wrote: > >> Hello! I enjoyed very much listening in on the default token provider >> work session last week in Austin, so thanks everyone

Re: [openstack-dev] [nova] Should be instance_dir in all nova compute node same ?

hi Timofei I don't have any specific use case, this issue is found while I am doing live migration testing, what I did is: 1. create 2 compute node, 2. create a nfs service on one of compute node, let's say node-2 and expose /opt/stack/date/nova/instances 3. mount

[openstack-dev] [TripleO] Summit Summary?

Hey Everyone - Forgive me if this has already been sent out - I looked through all of my emails and didn't see something yet. Can someone provide a summary of TripleO from the summit, for instance some of the output from the design sessions like the Trove, Magnum and some other teams have done?

[openstack-dev] [nova] Austin summit cells v2 session recap

Andrew Laski led a double session for cells v2 on Wednesday afternoon. The full session etherpad is here [1]. Andrew started with an overview of what's done and what's in progress. Note that some of the background on cells, what's been completed for cells v2 and what's being worked on is also

[openstack-dev] [Infra] Meeting Tuesday May 3rd at 19:00 UTC

Hi everyone, That was quite a summit last week! Now it's time to get back to IRC... The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday May 3rd, at 19:00 UTC in #openstack-meeting Meeting agenda available here:

Re: [openstack-dev] [Openstack-operators] Multi-region openstack liberty setup

Can you please provide all the endpoints being registered in the keystone? openstack endpoint list openstack service list And, also the command line used to create the endpoints for regiontwo From: kiran vemuri UH [mailto:kkvem...@uh.edu] Sent: Friday, April 29, 2016 12:02 PM To:

[openstack-dev] [oslo] Austin summit session recap(s)

Howday all, Since I know not everyone from the oslo community was able to attend the austin summit I just wanted to send out *my* version of the oslo sessions notes and next steps (others are free/encouraged to respond with there own) so that those folks can catch up and/or get up to speed.

Re: [openstack-dev] Timeframe for naming the P release?

But, the original spelling of the landing site is Plimoth Rock. There were still highway signs up in the 70's directing folks to "Plimoth Rock" --Rocky Who should know about rocks ;-) -Original Message- From: Brian Haley [mailto:brian.ha...@hpe.com] Sent: Monday, May 02, 2016 3:12 PM

Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

On Sun, May 1, 2016 at 12:54 AM Steven Dake (stdake) wrote: > Fellow core reviewers, > > We had a fantastic turnout at our fishbowl kubernetes as an underlay for > Kolla session. The etherpad documents the folks interested and discussion > at summit[1]. > > This proposal is

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

On Mon, May 2, 2016 at 7:07 AM Steven Dake (stdake) wrote: > Ryan had rightly pointed out that when we made the original proposal 9am > morning we had asked folks if they wanted to participate in a separate > repository. > > I don't think a separate repository is the correct

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

On Mon, May 2, 2016 at 5:26 PM, Clint Byrum wrote: > Hello! I enjoyed very much listening in on the default token provider > work session last week in Austin, so thanks everyone for participating > in that. I did not speak up then, because I wasn't really sure of this > idea

[openstack-dev] [glance] Categorization (previously centralization) of config options

Hello everyone, Just wanted to send a brief summary of the discussions at the summit. This list is not holistic however, it covers the relevant aspects that various stakeholders need to be aware of. * The current proposal is for centralizing config options, improving help text, adding

[openstack-dev] [keystone] Token providers and Fernet as the default

Hello! I enjoyed very much listening in on the default token provider work session last week in Austin, so thanks everyone for participating in that. I did not speak up then, because I wasn't really sure of this idea that has been bouncing around in my head, but now I think it's the case and we

[openstack-dev] [glance] [glare] Austin summit summary: Image sharing, community images, hierarchical image access, sharing in Glare

Hello everyone, Just wanted to send a brief summary of the discussions at the summit. This list is not holistic however, it covers the relevant aspects that various stakeholders need to be aware of. * Image sharing in it's current state is inadequate for the requirement of sharing an Image

Re: [openstack-dev] [glance] [glare] [heat] [tosca] [tacker] [murano] [magnum] [app-catalog] Austin summit summary: Generic cataloging and Glare v1 API

Added a few more tags to the subject line. On 5/2/16 7:05 PM, Nikhil Komawar wrote: > Hello everyone, > > Just wanted to send a brief summary of the discussions at the summit. > This list is not holistic however, it covers the relevant aspects that > various stakeholders need to be aware of. > >

[openstack-dev] [glance] [glare] [heat] [tosca] [tacker] Austin summit summary: Generic cataloging and Glare v1 API

Hello everyone, Just wanted to send a brief summary of the discussions at the summit. This list is not holistic however, it covers the relevant aspects that various stakeholders need to be aware of. * Glare is useful for different use cases in OpenStack including currently being asked for

[openstack-dev] [Glance] Updates, upcoming events and more awareness

Hello everyone, It was great to meet you (those who were) at the summit and missed those who couldn't come. So, for those who are waiting for updates I wanted to share some awareness of what's coming in the next few weeks. * I will be sending summaries of individual discussion items from the

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

Well, I don't think we should rely on ansible's config generation. We can't really as it's wired into ansible too much. jinja2 templates in Dockerfiles aren't connected to ansible in any way and are perfectly reusable. On 2 May 2016 at 16:13, Qiu Yu wrote: > On Mon, May 2,

Re: [openstack-dev] [octavia] amphora flavour and load balancer topology

Hi Lingxian, For #1, we create a nova flavor for the amphora in the devstack plugin. It is currently: nova flavor-create --is-public False m1.amphora ${OCTAVIA_AMP_FLAVOR_ID} 1024 2 1 I have not done extensive testing with these settings to optimize it. We were shooting for the minimum viable

Re: [openstack-dev] [devstack] - suggested development workflow without ./rejoin-stack.sh ?

Honestly those kind of major changes have to be discussed very carefully. On Tue, May 3, 2016 at 7:10 AM, Kevin Benton wrote: > This patch removed the ./rejoin-stack.sh script: > https://review.openstack.org/#/c/291453/ > > I relied on this heavily in my development VM which

Re: [openstack-dev] [devstack] - suggested development workflow without ./rejoin-stack.sh ?

Thanks for asking this, I would also like to know what the “real” answer is. But what I’ve found myself doing recently, since it was unwise to 100% count on rejoin-stack.sh, was to “do” everything via scripts and take periodic backups of same. You’re still only one power outage away from losing

[openstack-dev] [Coupler] Austin Summit vBrownBag slide

Hi, For those of you who are interested, you could find our slide at http://www.slideshare.net/zhipengh/storage-is-not-virtualized-enough-part-2-lets-do-service-chaining -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email:

[openstack-dev] [devstack] - suggested development workflow without ./rejoin-stack.sh ?

This patch removed the ./rejoin-stack.sh script: https://review.openstack.org/#/c/291453/ I relied on this heavily in my development VM which sees lots of restarts because of various things (VM becomes unresponsive in load testing, my laptop has a kernel panic, etc). Normally this was not a big

Re: [openstack-dev] Timeframe for naming the P release?

On 05/02/2016 02:53 PM, Shamail Tahir wrote: Hi everyone, When will we name the P release of OpenStack? We named two releases simultaneously (Newton and Ocata) during the Mitaka release cycle. This gave us the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata) releases. If we were to

[openstack-dev] [octavia] amphora flavour and load balancer topology

Hi, octavia guys, Recently, We have been thinking about deploying octavia into production (pre-production first in our case). Here are some questions/concerns that need your suggestions and feekback. 1. Octavia will use a default instance flavour, which is pre-configured, to create amphorae. Do

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

Were we looking at the same etherpad? I think the ‘inclusion criteria’ and ‘benefits of the proposal’ sections cover those two points. Are you referring to something else? Thanks, doug > On May 2, 2016, at 12:18 PM, Gal Sagie wrote: > > Maybe it can help if instead of

[openstack-dev] [zaqar] Zaqar meeting cancelled this week

Hi team, We cancelled the meeting today as most of the team is either OOO or in vacation after summit. We may also cancel the next meeting if there is no topic raised. Thanks. -- Cheers & Best regards, Fei Long Wang (王飞龙)

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

On Mon, May 2, 2016 at 12:38 PM, Steven Dake (stdake) wrote: > Yup but that didn't happen with kolla-mesos and I didn't catch it until 2 > weeks after it was locked in stone. At that point I asked for the ABI to > be unified to which I got a "shrug" and no action. > > If it

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

On 05/01/2016 05:03 PM, Steven Dake (stdake) wrote: Ryan had rightly pointed out that when we made the original proposal 9am morning we had asked folks if they wanted to participate in a separate repository. In Keystone, we are going to more and more repositories all the time. We started

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

On Mon, May 2, 2016 at 3:18 PM, Gal Sagie wrote: > Maybe it can help if instead of trying to define criteria to which projects > dont fit into > the stadium, try to define in your spec what IT IS, and for what purpose its > there. Well said. This came up multiple times in

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

Sorry for top-post... There's a third option : Using Feature branch for Kubernetes with a custom gerrit group * Feature branch can be sync'ed from Master periodically * Feature branch can have it's own separate gerrit group. * We can opt to merge from feature branch to master if necessary. * We

Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

+1 for kolla-kubernetes. On Mon, May 2, 2016 at 1:07 PM, Mauricio Lima wrote: > Just to clarify my vote. > > +1 for single repository > > 2016-05-02 14:11 GMT-03:00 Jeff Peeler : >> >> Also +1 for working on kolla-kubernetes. (Please read this thread

[openstack-dev] FW: [trove] Cancel weekly Trove meeting this week?

The Trove weekly meeting on the 4th of May is canceled. We can pick up any conversations that we need on IRC as required. Thanks, -amrith > -Original Message- > From: Amrith Kumar [mailto:amr...@tesora.com] > Sent: Monday, May 02, 2016 11:14 AM > To: OpenStack Development Mailing List

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

On Mon, May 2, 2016 at 1:23 PM, Jeff Peeler wrote: > On Sun, May 1, 2016 at 5:03 PM, Steven Dake (stdake) wrote: >> I don't think a separate repository is the correct approach based upon one >> off private conversations with folks at summit. Many people from

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

Jeff, What you propose is reasonable, but the timeline to make all that long term vision happen is time consuming and we want to get rolling now, not in t-4 to 6 weeks after we can sort out a kolla-docker and kolla-ansible split. FWIW It will make backporting a serious painful experience, and I

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

Yup but that didn't happen with kolla-mesos and I didn't catch it until 2 weeks after it was locked in stone. At that point I asked for the ABI to be unified to which I got a "shrug" and no action. If it has been in one repo, everyone would have seen the multiple ABIs and rejected the patch in

[openstack-dev] [nova] FYI: Citrix XenServer CI is disabled from voting

The Citrix XenServer CI is failing on most, if not all, changes it's running on today. Here is an example failure [1]. Devstack fails to setup due to a bad package install, so I'm guessing there is a problem in a mirror being used. I don't know if this is 100% failure but it's high enough to

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

Maybe it can help if instead of trying to define criteria to which projects dont fit into the stadium, try to define in your spec what IT IS, and for what purpose its there. On Mon, May 2, 2016 at 8:53 PM, Kyle Mestery wrote: > On Mon, May 2, 2016 at 12:22 PM, Armando M.

[openstack-dev] [Swift] going forward

At the summit last week, the Swift community spent a lot of time discussing the feature/hummingbird branch. (For those who don't know, the feature/hummingbird branch contains some parts of Swift which have been reimplemented in Go.) As a result of that summit discussion, we have a plan and a

Re: [openstack-dev] [magnum] Proposed Revision to Magnum's Mission

Hi team, As Adrian mentioned, we decided to narrow the scope of the Magnum project, and needed to revise Magnum’s mission statement to reflect our mission clearly and accurately. I would suggest to work on this effort as a team and created an etherpad for that:

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

I agree that we need one set of containers. Containers are kolla, deployment tools are consumers of kolla. We need our containers rock solid and decoupled from whatever is deploying them. Every company ops shop have their tooling and methods, let's help them. I'm not super in favor of ansible

Re: [openstack-dev] Timeframe for naming the P release?

On Mon, May 2, 2016 at 2:58 PM, Monty Taylor wrote: > On 05/02/2016 01:53 PM, Shamail Tahir wrote: > >> Hi everyone, >> >> When will we name the P release of OpenStack? We named two releases >> simultaneously (Newton and Ocata) during the Mitaka release cycle. This >>

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

+1 to one set of containers for all. If kolla-k8s needs tweaks to the abi, the request should go to the kolla core team (involving everyone) and discuss why they are needed/reasonable. This should be done regardless of if there are 1or 2 repo's in the end. Thanks, Kevin

[openstack-dev] [oslo] A bunch of releases

Just wanted to let people know about the new proposed releases (since there wasn't a IRC meeting today): If folks think these need updates or version number changes please comment on the review (or here). https://review.openstack.org/#/c/311812/ (the release proposals)

Re: [openstack-dev] Timeframe for naming the P release?

On 05/02/2016 01:53 PM, Shamail Tahir wrote: Hi everyone, When will we name the P release of OpenStack? We named two releases simultaneously (Newton and Ocata) during the Mitaka release cycle. This gave us the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata) releases. If we were to

[openstack-dev] Timeframe for naming the P release?

Hi everyone, When will we name the P release of OpenStack? We named two releases simultaneously (Newton and Ocata) during the Mitaka release cycle. This gave us the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata) releases. If we were to vote for the name of the P release soon (since

Re: [openstack-dev] [Nova] Could you tell me the best way to develop openstack in Windows?

Agreed. A VM running Linux is the only way to really develop for OpenStack. One could write the code on Windows and share it into the Linux VM to then be run via tox or another test tool. Both VirtualBox and VMWare support sharing a folder from your Windows host into the Linux guest. This way

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

On Mon, May 02, 2016 at 11:41:58AM -0700, Morgan Fainberg wrote: :On Mon, May 2, 2016 at 11:32 AM, Adam Young wrote: :> Kerberos would work, too, for deployments that prefer that form of :> Authentication. We can document this, but do not need to implement. :> :> :Never hurts

Re: [openstack-dev] [Nova] Could you tell me the best way to develop openstack in Windows?

On 2016-05-02 17:20:13 +0900 (+0900), �� wrote: [...] > But I��m using PyCharm in the Windows 7 but, It��s very hard to > programming and testing when I tried to change code little bit. [...] In my experience, when developing software which runs primarily on Linux it's a lot more complicated

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

On Mon, May 2, 2016 at 11:32 AM, Adam Young wrote: > On 04/26/2016 08:28 AM, Guangyu Suo wrote: > > Hello, oslo team > > For now, some sensitive options like password or token are configured as > plaintext, anyone who has the priviledge to read the configure file can get > the

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

On Tue, Apr 26, 2016 at 4:25 PM, Guangyu Suo wrote: > I think there is a little misunderstanding over here, the key point about > this problem is that you store your password as *plaintext* in the > configuration file, maybe this password is also the password of many other >

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

On 04/26/2016 08:28 AM, Guangyu Suo wrote: Hello, oslo team For now, some sensitive options like password or token are configured as plaintext, anyone who has the priviledge to read the configure file can get the real password, this may be a security problem that can't be unacceptable for

[openstack-dev] [kuryr] Question for Antoni Puimedon about load balancers and overlay networks

I am looking at https://www.openstack.org/videos/video/project-kuryr-docker-delivered-kubernetes-next , around 28:00. You have said that overlay networks are involved, and are now talking about load balancers. Is this Neutron LBaaS? As far as I know, a Neutron LBaaS instance is "one-armed"

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

On Sun, May 1, 2016 at 5:03 PM, Steven Dake (stdake) wrote: > I don't think a separate repository is the correct approach based upon one > off private conversations with folks at summit. Many people from that list > approached me and indicated they would like to see the work

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

I personally would like to see one set of defaults files for the default config and merging thereof. (the stuff in roles/*/defaults). There would be overlap there. A lot of the overlap involves things like reno, sphinx, documentation, gating, etc. During kolla-emsos, separate containers (IIRC)

Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

Just to clarify my vote. +1 for single repository 2016-05-02 14:11 GMT-03:00 Jeff Peeler : > Also +1 for working on kolla-kubernetes. (Please read this thread if > you haven't yet): > > http://lists.openstack.org/pipermail/openstack-dev/2016-May/093575.html > > On Mon, May

Re: [openstack-dev] [heat] update_allowed vs. immutable

Hi Praveen, The docs you referred to in the plugin guide is for the resource property attributes - they have nothing to do with parameters. This is an important distinction because there is also an "immutable" parameter attribute. The "immutable" property attribute was added because an

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

On Mon, May 2, 2016 at 12:22 PM, Armando M. wrote: > > > On 30 April 2016 at 14:24, Fawad Khaliq wrote: >> >> Hi folks, >> >> Hope everyone had a great summit in Austin and got back safe! :) >> >> At the design summit, we had a Neutron stadium evolution

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Mike Bayer's message of 2016-05-02 08:51:58 -0700: > > Well IMO that's actually often a problem. My goal across Openstack > projects in general is to allow them to make use of SQL more effectively > than they do right now; for example, in Neutron I am helping them to > move a

Re: [openstack-dev] [tripleo] composable roles team

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/01/2016 08:01 PM, Emilien Macchi wrote: >> If a feature can't land without disruption, then why not using a >> special branch to be merged once the feature is complete ? > > The problem is that during our work, some people will update the

[openstack-dev] [glance] Glare meeting SKIPPED this week.

Hi all, We skipped the meeting today as most of the team is either OOO or catching-up after summit. We have tentatively cancelled the next week's meeting as well however, if there is interest I can plan to open the agenda. -- Thanks, Nikhil

Re: [openstack-dev] [nova] Distributed Database

On 05/02/2016 11:51 AM, Mike Bayer wrote: On 05/02/2016 07:38 AM, Matthieu Simonin wrote: As far as we understand the idea of an ORM is to hide the relational database with an Object oriented API. I actually disagree with that completely. The reason ORMs are so maligned is because of this

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

Most of the code is not an overlap. We will preserve the ABI while customizing the ansible config generation (if we do end up using it). We can use some of what's in kolla as a starting point. I'd say the code overlap is a bootstrapping point for the project. -Ryan - Original Message

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

On 30 April 2016 at 15:42, Doug Wiegley wrote: > > On Apr 30, 2016, at 1:24 PM, Fawad Khaliq wrote: > > Hi folks, > > Hope everyone had a great summit in Austin and got back safe! :) > > At the design summit, we had a Neutron stadium evolution

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

On 30 April 2016 at 14:24, Fawad Khaliq wrote: > Hi folks, > > Hope everyone had a great summit in Austin and got back safe! :) > > At the design summit, we had a Neutron stadium evolution session, which > needs your immediate attention as it will impact many stakeholders of

Re: [openstack-dev] [nova] Distributed Database

On May 2, 2016, at 10:51 AM, Mike Bayer wrote: >> Concretely, we think that there are three possible approaches: >> 1) We can use the SQLAlchemy API as the common denominator between a >> relational and non-relational implementation of the db.api component. These >> two

Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

Also +1 for working on kolla-kubernetes. (Please read this thread if you haven't yet): http://lists.openstack.org/pipermail/openstack-dev/2016-May/093575.html On Mon, May 2, 2016 at 10:56 AM, Ryan Hallisey wrote: > +1 to start kolla-kubernetes work. > > - Original

Re: [openstack-dev] [magnum] Notes for Magnum design summit

Thanks for the write up Hongbin and thanks to all those who contributed to the design summit. A few comments on the summaries below. 6. Ironic Integration: https://etherpad.openstack.org/p/newton-magnum-ironic-integration - Start the implementation immediately - Prefer quick work-around for

[openstack-dev] [Ironic] Grenade testing work

During the OpenStack Summit it was decided that getting Grenade to work for Ironic would be the highest priority for the Ironic project. Because without Grenade, we won't have upgrade testing and we need upgrade testing for features we want to land to ensure we don't break anything. We will be

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

One thing we didn't talk about too much at the summit is the part of the spec that says we will reuse a bunch of ansible stuff to generate configs for the k8s case... Do we believe that code would be minimal and not impact separate repo's much or is the majority of the work in the end going to

[openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

Hello guys, Reading the conversation and analyzing a few trouble that happened with kolla-mesos and nothing can guarantee that will not happen the same with the K8S, as well as ensuring that the history will not lost. So, don't split the repo.

[openstack-dev] [heat] update_allowed vs. immutable

What is the difference between "update_allowed" and "immutable" parameters for a property? According to the plugin guide at http://docs.openstack.org/developer/heat/developing_guides/pluginguide.html: update_allowed: True if an existing resource can be updated, False means update is accomplished

Re: [openstack-dev] [openstack-health][QA] We need your feedbacks

On Mon, May 2, 2016 at 10:26 AM, Andrea Frittoli wrote: > I personally like Openstack Health UI/UX. I use it a lot a an initial > source of information. > Thanks to the OH team for all the great work on this! > +1 - This is a really awesome tool. I'll be writing up

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

On Mon, May 2, 2016 at 9:50 AM, Andreas Jaeger wrote: > On 05/02/2016 03:05 PM, Steven Dake (stdake) wrote: >> Swapnil, >> >> I gather this is what people want but this cannot be done with git and >> maintain history. To do this, we would have to "cp oldrepo/files to >>

Re: [openstack-dev] [nova] Distributed Database

On 05/02/2016 07:38 AM, Matthieu Simonin wrote: As far as we understand the idea of an ORM is to hide the relational database with an Object oriented API. I actually disagree with that completely. The reason ORMs are so maligned is because of this misconception; developer attempts to

Re: [openstack-dev] [glance] Interest in contributing to OpenStack

I guess this email answers a few questions I asked on my response email to your interest email. Thanks for clarifying! On 5/1/16 5:47 AM, Djimeli Konrad wrote: > Hello, > > With respect to my previous mail. I would just like to add that I am > aware the GSoC2016 and Outreachy2016 application

Re: [openstack-dev] [glance] Interest in contributing to OpenStack

Hi Djimeli, Thank you for expressing interest in contributing to projects in Glance. Glance community always welcomes passionate developers to contribute to our open source and open community platform. It's great to see that you've participated in GSOC and looking forward to contributing to

[openstack-dev] [vitrage] Vitrage meeting on May 4 - Newton design

Hi, Next Vitrage weekly meeting will be held on the coming Wednesday, May 4, at 9:00 UTC. Agenda: * Ohad and alexey_weyl will update on Austin Summit and their presentations[1][2] * We will start working on Vitrage Newton plan. I opened an etherpad for this purpose[3], please use it to add

Re: [openstack-dev] [Docs] Installation Guide Plans for Newton

On Mon, May 02, 2016 at 05:12:34PM +0200, Andreas Jaeger wrote: > On 05/02/2016 04:58 PM, Jim Rollenhagen wrote: > >On Mon, May 02, 2016 at 03:52:17PM +0200, Andreas Jaeger wrote: > >>On 05/02/2016 03:34 PM, Jim Rollenhagen wrote: > >>>On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote:

Re: [openstack-dev] [openstack-health][QA] We need your feedbacks

I personally like Openstack Health UI/UX. I use it a lot a an initial source of information. Thanks to the OH team for all the great work on this! And +1 to the new "feedback" link on the top and bottom of every page :) A few thoughts on my experience with OH. It can take a few clicks in OH to

[openstack-dev] [oslo] Reminder, no IRC meeting this week

Just a reminder to folk, I'll send out the summit notes today and get releases going but as we just had a summit last week, a meeting today on IRC doesn't seem needed (and most people may not be back yet from the summit anyway), Have a great week folks (and it was great seeing everyone)!

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

On Thu, Apr 28, 2016 at 01:30:40PM -0500, Sean McGinnis wrote: > The results are in! > > We took a look at the SurveyMonkey results today, and we have now > formally set the dates and locations for the Cinder Newtone midcycle. > > All are welcome and encouraged to attend! > >

[openstack-dev] [trove] Cancel weekly Trove meeting this week?

We all had a week full of meetings last week and I'm not sure that we have anything significantly new on the agenda for the weekly meeting on the 4th. So, if I don't hear anyone object, I'll send an email out by 4pm Eastern Time today canceling the Trove weekly meeting for the 4th of May.

Re: [openstack-dev] [Docs] Installation Guide Plans for Newton

On 05/02/2016 04:58 PM, Jim Rollenhagen wrote: On Mon, May 02, 2016 at 03:52:17PM +0200, Andreas Jaeger wrote: On 05/02/2016 03:34 PM, Jim Rollenhagen wrote: On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote: Greetings from Austin! Yesterday we held the Install Guide planning

Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

+1 to start kolla-kubernetes work. - Original Message - From: "Swapnil Kulkarni" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Monday, May 2, 2016 12:59:40 AM Subject: Re: [openstack-dev]

Re: [openstack-dev] [Docs] Installation Guide Plans for Newton

On Mon, May 02, 2016 at 03:52:17PM +0200, Andreas Jaeger wrote: > On 05/02/2016 03:34 PM, Jim Rollenhagen wrote: > >On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote: > >>Greetings from Austin! > >> > >>Yesterday we held the Install Guide planning workgroup. It was a full room, >

Re: [openstack-dev] [oslo] Backwards compatibility policy

This was a good session lead by Robert to fully understand the repercussions of not ensuring backward compatibility guidelines. In layman's terms, an Oslo API change made in Mitaka (the last release) must remain fully backward compatible throughout the entire Newton release (the current release).

Re: [openstack-dev] [tc] Leadership training dates - please confirm attendance

On Fri, Apr 22, 2016 at 4:57 PM, Colette Alexander wrote: > On Thu, Apr 21, 2016 at 10:42 AM, Doug Hellmann wrote: >> >> Excerpts from Colette Alexander's message of 2016-04-21 08:07:52 -0700: >> >> > >> > Hi everyone, >> > >> > Just checking in

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

It seems for me that we have a dilemma between security (abstaining from creating a core group which may overuse their rights in kolla repo) and usability (not having multiple repos, which we experienced badly in the kolla-mesos era). I don't find the argument about having k8s ecosystem in

Re: [openstack-dev] [oslo] Removing Nova specifics from oslo.log

Julien, As mentioned I have been working thru the App Agnostic Parameters blueprint that will cover review of context attributes and kwarg specific use of oslo.log. Presently due to legacy nova usage this current pattern is needed as it. There was also a discussion at Austin with Michael Still

Re: [openstack-dev] [QA][RFC] Skip this week meeting

I don't have anything urgent so fine with me. Andrea On Mon, 2 May 2016, 3:04 p.m. Masayuki Igawa, wrote: > Hi QA guys, > > We have very few topic this week to discuss. So I think we should skip > this week meeting. > Any thoughts? > > Best Regards, > -- Masayuki

[openstack-dev] [QA][RFC] Skip this week meeting

Hi QA guys, We have very few topic this week to discuss. So I think we should skip this week meeting. Any thoughts? Best Regards, -- Masayuki Igawa __ OpenStack Development Mailing List (not for usage questions)

  1   2   >