Re: [openstack-dev] [all]call for contributors for Tricircle project - for massive distributed edge clouds and large scale cloud.

Hi Chaoyi, At a meeting today, we had a great update from you. I don't write any details here but I'm quite happy with that. I believe that we will have awesome contributors and the Tricircle become one of important projects soon. Cheers, Shinobu On Mon, Apr 25, 2016 at 1:59 PM, joehuang

Re: [openstack-dev] [neutron][taas] TaaS meetup in Austin

Hi, It will be held on 9:30 a.m., Meeting Room 400 (Level 4, Hilton Austin). Regards, Soichi From: Anil Rao [mailto:anil@gigamon.com] Sent: Friday, April 29, 2016 2:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron][taas]

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

Hi, >From the first sight there are no restrictions for instance_path option. Could you please provide some details about the use case? I wonder would this functionality be really useful for cloud-operators, or we just should add description to instance path option, forcing to use the same path

Re: [openstack-dev] [neutron][taas] TaaS meetup in Austin

Hi, > It will be held on 9:30 a.m., Meeting Room 400 (Level 4, Hilton Austin). This is just an announcement of rendezvous point. We may move to somewhere else if necessary. From: Shigeta, Soichi [mailto:shigeta.soi...@jp.fujitsu.com] Sent: Friday, April 29, 2016 6:40 PM To: OpenStack

Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

Hi Eli, Copy that, I will consider that. Thanks. Regards Mike Date: Thu, 28 Apr 2016 17:05:44 +0800 From: Eli Qiao > To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Magnum]

Re: [openstack-dev] [neutron] [qos] gathering Friday 9:30

Hi Miguel, Nate and I have a conflicting meeting, about FWaaS, at 9:30. I’m reaching out to him now to see how we might fan out to get coverage. Margaret -- Margaret Frances Eng 4, Prodt Dev Engineering > On Apr 28, 2016, at 6:02 PM, Miguel Angel Ajo Pelayo > wrote:

[openstack-dev] [qa] Summary of design summit for Newton

Hi QA-team, Thanks for joining QA sessions on OpenStack Summit Austin. They were interesting and good to get directions to move forward in this development cycle. This is a summary of these sessions for next steps and hope this helps our works. 1. Tempest: Cleanup

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

On 4/28/2016 8:54 PM, Edward Leafe wrote: On Apr 28, 2016, at 5:35 PM, Clint Byrum wrote: - Vitess [2] is a proven technology that serves _every_ request to Youtube, and provides a familiar SQL interface with sharding built in. Shard by project ID and you can just use

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

Hello, My name is Djimeli Konrad a second year computer science student from the University of Buea Cameroon, Africa. I am GSoC 2015 participant, and I have also worked on some open-source projects on github (http://github.com/djkonro) and sourceforge

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

On Fri, 29 Apr 2016, Matt Riedemann wrote: So, we're all here in person this week (with 1 day left). The Nova team has a meetup session all day (Salon A in the Hilton). Clint/Ed, can you guys show up to that and bring these issues up in person so we can actually talk through this? Preferably

[openstack-dev] [nova] next min libvirt?

We've just landed the libvirt min to bump us up to 1.2.1 required. It's probably a good time consider the appropriate bump for Otaca. By that time our Ubuntu LTS will be 16.04 (libvirt 1.3.1), RHEL 7.1 (1.2.8). Additionally Debian Jessie has 1.2.9. RHEL 7.2 is at 1.2.17. My suggestion is we set

[openstack-dev] [kolla] Meetup in Salon B - split between Magnum and Kolal

Hey folks, The meet up room for this morning is split between two rooms so we will be sharing a room in Salon B. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla] Deploying kolla from a container?

So network interface is an inteface that APIs will bind into. That means it's network which openstack stuff travels on. Neutron_external_iface is iface tenant networks will be placed on. In you r case you could use eth0 as network and eth1 as neutron external. If it has IP that's ok...it simply

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

Excerpts from Matt Riedemann's message of 2016-04-29 05:38:17 -0700: > > So, we're all here in person this week (with 1 day left). The Nova team > has a meetup session all day (Salon A in the Hilton). Clint/Ed, can you > guys show up to that and bring these issues up in person so we can >

Re: [openstack-dev] [heat]informal meetup during summit

I will be there after 15 min 28 апр. 2016 г. 7:14 PM пользователь "Rico Lin" написал: > *Tomorrow 10:00 am at alta's cafe* > > See you guys have there:) > > http://altascafe.com/ > > map >

Re: [openstack-dev] [neutron] Social at the summit

A good number of us (about 20) got to Bangers around 6:15 and stayed there until around 10. There were plenty of tables available. We had a great time On Thu, Apr 28, 2016 at 7:00 PM, Zhou, Han wrote: > When I went there I didn't see any of our folks so I went to another >

[openstack-dev] [horizon][release] freeze timelines for horizon in newton

In the Trove review of the release schedule this morning, and in the retrospective of the mitaka release process, one question which was raised was the linkage between projects like Trove and Horizon. This came up in the specific context of the fact that projects like Trove (in the form of the

Re: [openstack-dev] [neutron] Discussing DLMs in the Unplugged Track

Hi guys, We'll meet at 11:00 at Salon C, Hilton. John. On Sun, Apr 24, 2016 at 8:59 AM, Joshua Harlow wrote: > I'll try to be there as well, since I know a little bit about tooz ;) > > -Josh > > > Gary Kotton wrote: >> >> Hi, >> I suggest that you speak with Kobi Samoray

Re: [openstack-dev] [Neutron] L3 HA testing on scale

Folks, change https://review.openstack.org/#/c/310419/ proposed to performance-docs. Thanks Ann, soon it'll appear on http://docs.openstack.org/developer/performance-docs/# Cheers, Dina On Wed, Apr 20, 2016 at 10:56 PM, Edgar Magana wrote: > Indeed it will be a

Re: [openstack-dev] [nova] next min libvirt?

On 04/29/2016 10:28 AM, Daniel P. Berrange wrote: > On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: >> We've just landed the libvirt min to bump us up to 1.2.1 required. It's >> probably a good time consider the appropriate bump for Otaca. >> >> By that time our Ubuntu LTS will be

Re: [openstack-dev] [nova] next min libvirt?

On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > We've just landed the libvirt min to bump us up to 1.2.1 required. It's > probably a good time consider the appropriate bump for Otaca. > > By that time our Ubuntu LTS will be 16.04 (libvirt 1.3.1), RHEL 7.1 > (1.2.8). Additionally

[openstack-dev] [neutron] dvr with ovs-dpdk.

Hi If any of the dvr team are around I would love to Meet with ye to discuss how to make dvr work efficiently when using ovs with the dpdk datapath. Ill be around the Hilton all day and am currently in room 400 but if anyone wants to meetup to Discuss this let me know Regards Seán

[openstack-dev] [nova][neutron] restarting SR-IOV/PCI Passthrough meeting

Hi all, I would like to restart the SR-IOV/PCI Pass-through. The main focus is to improve CI coverage and fixing bugs in nova side. I updated the agenda etherpad [1] with stuff to cover on the next meeting Mar 3rd 2016. The meeting will be biweekly. I like that the Mellanox/Intel and other

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

Hey folks, This vote passed with 8 core reviewers +1ing the retirement of the kolla-mesos repository. As such I will submit patches in the following week to retire this project and remove it from the technical committee's governance repository for the Kolla Project. Regards -steve From:

Re: [openstack-dev] [Nova] RFC Host Maintenance

Hi, Maintenance was discussed in the OpenStack summit in "Ops: Nova Maintenance - how do you do it?" It was decided the best alternative is just to expose the nova-compute disabled_reason to owner of the server. This field can then have URL to more detailed status given in external tool.

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

Adrian, fyi, there's one more already filed by Josh - https://review.openstack.org/#/c/310941/ -- Dims On Fri, Apr 29, 2016 at 7:47 PM, Adrian Otto wrote: > Magnum Team, > > In accordance with our Fishbowl discussion yesterday at the Newton Design > Summit in Austin,

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

On 4/29/2016 5:32 PM, Murray, Paul (HP Cloud) wrote: The following summarizes status of the main topics relating to live migration after the Newton design summit. Please feel free to correct any inaccuracies or add additional information. Paul

Re: [openstack-dev] [Ceph][ceilometer][libvirt] Libvirt error during instance disk allocation metering

Hi Ceph devs, I raise this bug again because as Ceph becomes more popular, our customer suffers from it and I have no solution for it. *Is there anyway to get the usage of a disk which is a Ceph volume? (Not sure if the term is right or not)* Ceilometer use libvirt.domain.blockInfo(device) to

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

Hi team, For reference, below is a summary of the discussions/decisions in Austin design summit. Please feel free to point out if anything is incorrect or incomplete. Thanks. 1. Bay driver: https://etherpad.openstack.org/p/newton-magnum-bay-driver - Refactor existing code into bay drivers -

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

Magnum Team, In accordance with our Fishbowl discussion yesterday at the Newton Design Summit in Austin, I have proposed the following revision to Magnum’s mission statement: https://review.openstack.org/311476 The idea is to narrow the scope of our Magnum project to allow us to focus on

Re: [openstack-dev] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

Hi Bogdan, Thank you for sharing this! I'll need to familiarize myself with this Jepsen thing, but overall it looks interesting. As it turns out, we already run Galera in multi-writer mode in Fuel unintentionally in the case, when the active MySQL node goes down, HAProxy starts opening

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

Hi, Now, we are making OpenStack-Health[1] which is a dashboard for visualizing test results of OpenStack CI jobs. This is heavily under development mode but works, you can use it now. We'd like to get your feedback to make it better UI/UX. So, if you have any comments or feedbacks, please feel

Re: [openstack-dev] [nova] next min libvirt?

On 4/29/2016 10:28 AM, Daniel P. Berrange wrote: On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: We've just landed the libvirt min to bump us up to 1.2.1 required. It's probably a good time consider the appropriate bump for Otaca. By that time our Ubuntu LTS will be 16.04 (libvirt

[openstack-dev] [oslo] Backwards compatibility policy

Yesterday, in https://etherpad.openstack.org/p/newton-oslo-backwards-compat-testing we actually reached consensus - well, 7/10 for and noone against - doing 1 cycle backwards compatibility in Oslo. That means that after we release a thing, code using it must not break (due to an Oslo change)

[openstack-dev] Multi-region openstack liberty setup

Hello All, I am trying to deploy multi-region liberty OpenStack setup and I am following http://docs.openstack.org/liberty/install-guide-ubuntu/ to bring up each node. I was able to bring up region one successfully. Now while bringing up region2, when I try to create keystone service while

Re: [openstack-dev] [horizon][release] freeze timelines for horizon in newton

This has been discussed (just now) in the release management plan (https://etherpad.openstack.org/p/newton-relmgt-plan) See point 8 under Communication/Governance Changes. From an immediate standpoint, the RC phase of this cycle will be much stricter to prevent late breakages. Going forward,

[openstack-dev] [tripleo] composable roles team

Hi, One of the most urgent tasks we need to achieve in TripleO during Newton cycle is the composable roles support. So we decided to build a team that would focus on it during the next weeks. We started this etherpad: https://etherpad.openstack.org/p/tripleo-composable-roles-work So anyone can

[openstack-dev] Requirements for becoming approved official project

Hi Tom, First sorry for bothering you -; We are trying to make the tricircle project [1] one of the opnestack official projects. And we are referring to project team guide to make sure what are requirements. [2]. Reading this guide, what we need to consider right now is open development, I think

Re: [openstack-dev] [kolla] Deploying kolla from a container?

But if I use eth0 (public internet) for network_interface and the VM's public IPv4 as the kolla_internal_vip_address, I'm not sure it'll work because the prechecks does the following: TASK: [prechecks | Checking if kolla_internal_vip_address and kolla_external_vip_address are not pingable from

[openstack-dev] Please propose and join me for the first meeting of new Project Cloudlet

Hi all I am trying to organize a new module called "Cloudlet" in OpenStack. At the Product Working Group and after discussions with Infrastructure team decided to start putting together pieces of past work and plan for new "Cloudlet" project for Edge Cloud Services using Cloudlet in

[openstack-dev] [Nova] Live Migration: Austin summit update

The following summarizes status of the main topics relating to live migration after the Newton design summit. Please feel free to correct any inaccuracies or add additional information. Paul - Libvirt storage pools The storage pools

Re: [openstack-dev] [magnum] Seek advices for a licence issue

Hi Jay, Thanks for taking the responsibility. I have approved the blueprint [1] and assigned it to you. According to the decision in the design summit, we prefer to have a new bay type for DC/OS, and the original mesos bay should be untouched until the new DC/OS bay is mature. I am looking

[openstack-dev] [heat] Summit Friday Night Dinner

Torchy's Tacos 1311 S 1st St Austin, TX 78704 It's about a 20 minute walk from the Radisson (pretty much straight down Congress Ave) and then over a block. Meeting in the Radisson lobby at 7:10 to walk over. Apologies in advance if we see another snake and I jump on someone's shoulders

[openstack-dev] [trove] final notes from Trove summit design summit sessions

Here is the updated (final) notes from the Trove design summit in Austin, TX. Some changes from yesterday's email are highlighted. Changes are marked with "::NOTE::" -amrith Python3 support - make python34 a voting test in the gate (was already done, so no action required) - peterstac to

[openstack-dev] [heat][qa] devstack plugin

Hi Heat-team, Thanks for talking the topic of devstack plugin with us in Austin summit. As you know, many projects have started to use devstack plugin in each project repo. and it is nice to use the plugin in heat also. A good sample is ironic one: