Re: [openstack-dev] [neutron]CIDR overlapping

O, it's being set to "True" in devstack installation. Thanks for clarification. Best Regards Chaoyi Huang (joehuang) From: Kevin Benton [ke...@benton.pub] Sent: 14 February 2017 12:17 To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

[openstack-dev] [Tricircle] Heading for PTG

Hi folks, I am heading for Atlanta PTG as the representative of Tricircle project, if you are interested in Tricircle project and will also attend Atlanta PTG, we can meet and discuss some topics there. BR Zhiyuan -- BR Zhiyuan

Re: [openstack-dev] [heat][tripleo][mistral][all]PTG: Cross-Project: OpenStack Orchestration Integration

Ok, thanks Rico. Keep us updated on the schedule changes. I’m currently finalizing the schedule for Mistral, for now I’ll leave Thursday 11.00-12.00 blank. Renat Akhmerov @Nokia > On 14 Feb 2017, at 10:49, Rico Lin wrote: > > Let's move the schedule toThursday

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 15th February

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 15th February in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

Re: [openstack-dev] [tripleo] Blueprints for DPDK in OvS2.6

Oops. Forgot to update, We have changed the name of the BP as the "dot" in the BP name was not going well with the gerrit reviews. The new URLs are (dot changed to dash): https://blueprints.launchpad.net/tripleo/+spec/ovs-2-6-dpdk

[openstack-dev] [all][requirements] Eventlet verion bump coming?

Hi All, So there is a new version of eventlet out and we refused to bump it late in the ocata cycle but now that we're early in the pike cycle I think we're okay to do it. The last time[1] we tried to bump eventlet it was pretty rocky and we decided that we'd need a short term group of people

[openstack-dev] [Oslo] Oslo log files

We got cool logos in different format, just use them :-) I’m excited to finally be able to share final project logo files with you. Inside this folder, you’ll find full-color and one-color versions of the logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use them on

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

So from my perspective I can tell that problem is completely in architecture and even without something outside of Neutron we cannot solve that. Two releases ago I started to work on hardening that feature but all my ideas was killed by Armando and Assaf. The decided that adding outside

[openstack-dev] Call for mentors and funding - Outreachy

Hello everyone, An update on the Outreachy program, including a request for volunteer mentors and funding. For those of you who are not aware, Outreachy helps people from underrepresented groups get involved in free and open source software by matching interns with established mentors in the

Re: [openstack-dev] [neutron]CIDR overlapping

Do you have allow_overlapping_ips set to True? On Mon, Feb 13, 2017 at 7:56 PM, joehuang wrote: > Hello, > > During the regression test, I find that Neutron allows CIDR overlapping in > same project. > > neutron --os-region-name RegionOne net-create dup-net1 > neutron

Re: [openstack-dev] [heat][tripleo][mistral][all]PTG: Cross-Project: OpenStack Orchestration Integration

Let's move the schedule toThursday morning 11:00 am to 12:00 pm in the same room. Hope that schedule work for all:) Also, I will ask if Mon - Tue is available or not, but there might be more cross-project sessions we have to not to conflict with them. 2017-02-14 10:02 GMT+08:00 Renat Akhmerov

[openstack-dev] [neutron] Neutron logo files

We got some cool new logos. Check them out! -- Forwarded message -- From: "Heidi Joy Tretheway" Date: Feb 13, 2017 15:02 Subject: Neutron logo files To: , "Armando M." Cc: Hi Armando and Kevin, I’m excited to finally

Re: [openstack-dev] [heat][magnum][murano][sahara][tripleo][mistral][all]PTG: Cross-Project:Orchestration feedback and announcement

> > > Aren’t we supposed to have all cross-project sessions on Mon-Tue? > That is an interesting way to do it, althrough the cross project effort mentioned by PTG is refering to release goals, Architecture workgroup, any other workgroups. I will ask if those time is available for this kind of

[openstack-dev] [neutron]CIDR overlapping

Hello, During the regression test, I find that Neutron allows CIDR overlapping in same project. neutron --os-region-name RegionOne net-create dup-net1 neutron --os-region-name RegionOne net-create dup-net2 neutron --os-region-name RegionOne subnet-create dup-net1 20.0.1.0/24 neutron

[openstack-dev] [kolla] Mascot

And here we are, our mascot:) Feel free to use it in any Kolla related presentation or tattoo studio. https://www.dropbox.com/sh/94pukquiw425ji2/AAAl2wVmm72KHPLCAzR6Uboha?dl=0 __ OpenStack Development Mailing List (not for

[openstack-dev] [Cinder] Project mascot available

For your viewing and slide designing pleasure... We have the official mascot completed from the illustrators. Multiple formats are available from here: https://www.dropbox.com/sh/8s3859c6qulu1m3/AABu_rIyuBM_bZmfGkagUXhua?dl=0 Stay golden, pony boy. Sean

[openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Team, I've got this email from Heidi. I see 3 options : 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg . 2. Re-design a new logo that "meets" OpenStack "requirements". 3. Pick-up the one proposed (see below). Personally, I would vote for keeping our existing logo (1.)

Re: [openstack-dev] [keystone] mascot

this looks great! On Mon, Feb 13, 2017 at 9:28 PM, Lance Bragstad wrote: > Good news! We just got the final revision for our official keystone mascot > [0]! > > I have a note on my todo list to put together a basic chart deck with > them. I'll send out a link for folks to

[openstack-dev] [keystone] mascot

Good news! We just got the final revision for our official keystone mascot [0]! I have a note on my todo list to put together a basic chart deck with them. I'll send out a link for folks to use when I get them done. [0] https://www.dropbox.com/sh/0owldvy0u5y4yk9/AAB5Q95wYj- oaiisneKbnEiDa?dl=0

Re: [openstack-dev] [heat][tripleo][mistral][all]PTG: Cross-Project: OpenStack Orchestration Integration

> On 13 Feb 2017, at 19:30, Emilien Macchi wrote: > > > > On Mon, Feb 13, 2017 at 4:48 AM, Rico Lin > wrote: > Dear all > > PTG is approaching, we have few ideas around TripleO team ([1] and [2]) about > use

Re: [openstack-dev] [heat][magnum][murano][sahara][tripleo][mistral][all]PTG: Cross-Project:Orchestration feedback and announcement

Hi Rico, Aren’t we supposed to have all cross-project sessions on Mon-Tue? The time slot you mentioned is kind of ok, I can be there (although earlier would be better) but starting Wed we all have time dedicated to specific project discussions. Renat Akhmerov @Nokia > On 13 Feb 2017, at

[openstack-dev] [mistral][logo][mascot] Fwd: Mistral logo files

Hi, our logos are finally ready! Renat Akhmerov @Nokia > Begin forwarded message: > > From: Heidi Joy Tretheway > Subject: Mistral logo files > Date: 14 February 2017 at 05:00:56 GMT+7 > To: Renat Akhmerov > > Hi Renat, > > I’m excited to

[openstack-dev] [neutron]Find a property way to face agent rpc message lost.

Currently, neutron agent report its state through rpc. The message will be fetched by neutron server and store the latest info into db. There may be some problems found in the scenarios of public cloud.[1]. Neutron & its agents and nova & its services(nova compute) may hit the same problem. So

[openstack-dev] [zaqar] Zaqar logo files

Hi team, Here is the final version of Zaqar mascot. Forwarded Message Subject:Zaqar logo files Date: Mon, 13 Feb 2017 15:26:12 -0800 From: Heidi Joy Tretheway To: Fei Long Wang Hi Fei Long, I’m excited to

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Excerpts from Ian Cordasco's message of 2017-02-13 15:15:12 -0500: > -Original Message- > From: Clint Byrum > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: February 13, 2017 at 13:41:00 > To: 

Re: [openstack-dev] [monasca] Ideas to work on

Hi Anqi, See my comments listed below. Regards --Roland From: An Qi YL Lu > Date: Sunday, February 12, 2017 at 8:29 PM To: Roland Hochmuth > Cc: OpenStack List

[openstack-dev] [Horizon] Final project mascot

Hi folks, Here's the final mascot/logo from the Foundation. Richard -- Forwarded message -- From: Heidi Joy Tretheway Date: 14 February 2017 at 08:49 Subject: Horizon project mascot To: Rob Cresswell , Richard Jones <

[openstack-dev] [all] Moving coverage jobs to check queue

Hello, In a prior thread we discussed moving coverage jobs from "post" jobs to the check queue [1]. Firstly, if you have no idea what I'm talking about, the coverage jobs run the unit tests under the coverage tool [2] and produce some output like [3] which identifies which parts of the code have

[openstack-dev] [QA] [all] Pike PTG QA Input / Feedback Session

Hi folks, at the PTG in Atlanta we will schedule a session [0] to collect and discuss feedback and input from the community on existing QA projects. We will use the resulting material in a later session to set priorities of the QA team for Pike. Note that for Tempest plugins specifically there

[openstack-dev] [QA] Quality Assurance logo files

-- Forwarded message - From: Heidi Joy Tretheway Date: Mon, Feb 13, 2017 at 10:09 PM Subject: Quality Assurance logo files To: , Hi Ken’ichi and Andrea, I’m excited to finally be able to share final

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

On Thu, Feb 9, 2017 at 7:47 AM, Takashi Yamamoto wrote: > i plan to cut a release for networking-midonet once relevant projects get > ready. > ie. neutron-vpnaas, tap-as-a-service https://review.openstack.org/#/c/429437/ > > On Thu, Feb 9, 2017 at 1:16 AM, Armando M.

[openstack-dev] [QA] Pike PTG Schedule

Hello team, I did some work on the etherpad [0] to organise the QA PTG schedule based on the proposed sessions. I separated discussion sessions from hands-on type of actives. I thing the former will require a fixed schedule so folks may know when to pop-in to attend; the latter may happen more

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

On Tue, Feb 14, 2017 at 8:15 AM, Doug Hellmann wrote: > Excerpts from Takashi Yamamoto's message of 2017-02-14 07:31:34 +0900: >> hi, >> >> On Tue, Feb 14, 2017 at 1:54 AM, Doug Hellmann wrote: >> > Excerpts from Takashi Yamamoto's message of

[openstack-dev] Fwd: Docs project mascot

Hi everyone, Here's the final docs logo from Foundation. Lana Forwarded Message Subject:Docs project mascot Date: Mon, 13 Feb 2017 13:38:46 -0800 From: Heidi Joy Tretheway To: Alexandra Settle , Lana Brindley

Re: [openstack-dev] [networking-sfc] What resources can and can't be reused

Hi Igor, The list of rules are correct. Best regards, Cathy From: Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com] Sent: Monday, February 13, 2017 1:27 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [networking-sfc] What resources can

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

Excerpts from Takashi Yamamoto's message of 2017-02-14 07:31:34 +0900: > hi, > > On Tue, Feb 14, 2017 at 1:54 AM, Doug Hellmann wrote: > > Excerpts from Takashi Yamamoto's message of 2017-02-06 10:32:10 +0900: > >> On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto

[openstack-dev] [keystone] Pike PTG scheduling

Hey folks, We've had an etherpad [0] floating for the last few weeks collecting ideas for PTG sessions. I spent today finalizing several of the existing topics and porting others from various sources. While I think this is a pretty exhaustive list, I'm leaving it open for any last minute

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

On Mon, Feb 13, 2017 at 8:39 PM, Clint Byrum wrote: [snip] > Any attempt at versioning that is not git, will frustrate any git user. > This cat's already out of the bag, but I'd suggest adding git repositories > as a blob container type and finding a way to allow git to

[openstack-dev] [nova] Pike PTG Planning

I'm working on organizing the nova-ptg-pike etherpad [1] which involves trying to come up with a rough schedule to cover topics that might impact other projects. I'm starting by simply grouping related topics (placement, cells, quotas, etc) and then figure out what times work best for

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

hi, On Tue, Feb 14, 2017 at 1:54 AM, Doug Hellmann wrote: > Excerpts from Takashi Yamamoto's message of 2017-02-06 10:32:10 +0900: >> On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto >> wrote: >> > hi, >> > >> > On Fri, Jan 27, 2017 at 7:46 AM,

Re: [openstack-dev] [networking-sfc] What resources can and can't be reused

Hi Louis, Yes, that makes sense - thanks for the feedback and the responses on my points. Best regards, Igor. From: Henry Fourie [mailto:louis.fou...@huawei.com] Sent: Monday, February 13, 2017 9:15 PM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [networking-sfc] What resources can and can't be reused

Igor, For #6, the requirement on source-port for a flow-classifier is only for the OVS driver. This is not a restriction for other backend drivers. In the case where there is no need for a sfc proxy to re-classify traffic returned from the egress port of a SF, i.e., the SF is NSH-aware and it

Re: [openstack-dev] [networking-sfc] What resources can and can't be reused

Igor, See inline. -Louis From: Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com] Sent: Monday, February 13, 2017 11:12 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [networking-sfc] What resources can and can't be reused Hi

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are feverish to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. Clean up

Re: [openstack-dev] [networking-sfc] What resources can and can't be reused

Hi Cathy, Relax only a couple of them. For Ocata I'm looking at disabling #6 if the chain/graph doesn't include sfc proxies (#6 seems to only be necessary if there are sfc proxies [1]). For Pike it would be interesting to make port-pair-groups completely reusable, as long as the flow

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

-Original Message- From: Clint Byrum Reply: OpenStack Development Mailing List (not for usage questions) Date: February 13, 2017 at 13:41:00 To: openstack-dev Subject:  Re: [openstack-dev]

Re: [openstack-dev] [networking-sfc] What resources can and can't be reused

Hi Igor, Before we dive into evaluation of the rules you listed below, I would like to understand whether you are suggesting to enforce the rules or relax the rules/constraints you listed? Could you clarify it? Thanks, Cathy From: Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com]

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Excerpts from Mikhail Fedosin's message of 2017-02-13 18:23:19 +0300: > Hello! > > > Let me quickly describe my vision of the problem. I asked this question to > Brian last Friday, because it is evident that the projects have the > intersection in functionality. For this reason, I proposed to

[openstack-dev] [Tacker] Tacker upgrade vnf

Hi Tacker folks, I have my own consideration about vnf upgrade. Please correct me if i am wrong. As i saw that tacker supports the vnf update when vnfd and vnfd_id do not change. What about the situation of upgrading vnf, for instance, i would like to upgrade my vnf which is deployed with one

[openstack-dev] [networking-sfc] What resources can and can't be reused

Hi networking-sfc, As part of my work regarding SFC Encapsulation and SFC Graphs, I exercised the API to understand exactly what resources can be reused, to possibly relax a few of the constraints when a chain is encapsulated end-to-end. I'm requesting that the leaders and cores take a look at

[openstack-dev] [gnocchi]

__ 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] [tripleo] TripleO Ocata release blockers

On 02/12/2017 02:24 PM, Emilien Macchi wrote: Quick updates: - All FFEs patches have been merged except: https://review.openstack.org/#/c/330050/ - so we're green on this side. - Upgrade team is still working on automation to upgrade from newton to ocata. - ovb-updates (CI job with IPv6)

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

On 02/13/2017 07:47 AM, Ian Cordasco wrote: > -Original Message- > From: Clint Byrum > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: February 12, 2017 at 20:09:04 > To: openstack-dev

[openstack-dev] [ironic][ptg] Evening gathering and Attendance

Greetings everyone! We are attempting to put together a team gathering for one evening during the PTG. As such, we’ve created a doodle poll[0]. Please fill out the poll as soon as possible so we can determine the number of people who will be up for attending an evening gathering, as well as

[openstack-dev] [monasca] Log Query API Design

Hi, For those interested, I have been expanding on the initial design for a simple query API to add to monasca-log-api. The design is available here: https://wiki.openstack.org/wiki/Monasca/Logging/Query_API_Design#Design:_Log_Listing I have proposed the initial "Log Listing" part of the API

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Okay, it seems I did not express myself very well :) But then there is a rhetorical question: if it's officially recommended to use the service with the name that starts with "S", why does Nova use a service with the name beginning with "G" to store its images? As you may know Glare is a proxy to

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

-Original Message- From: Jeremy Stanley Reply: OpenStack Development Mailing List (not for usage questions) Date: February 13, 2017 at 10:14:24 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [all] [ptg] [goals] Pike WSGI Goal Planning

Emilien Macchi wrote: > I created https://etherpad.openstack.org/p/ptg-pike-wsgi so we can > start discussing on this goal. > Thierry confirmed to me that we would have a room on either Monday or > Tuesday. Please let us know in the etherpad if you have schedule > constraints. Sorry if I was

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

Excerpts from Takashi Yamamoto's message of 2017-02-06 10:32:10 +0900: > On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto > wrote: > > hi, > > > > On Fri, Jan 27, 2017 at 7:46 AM, Doug Hellmann > > wrote: > >> Excerpts from Takashi Yamamoto's

Re: [openstack-dev] [api] [arch] API WG PTG planning

On Mon, 13 Feb 2017, Thierry Carrez wrote: So we have indeed an extra room that we could dedicate to the API WG (Monday and/or Tuesday) -- the only drawback is that it won't appear in printed maps or schedule since those were sent to print already. ttx and I talked about this in IRC and came

Re: [openstack-dev] [api] API WG PTG planning

Thierry Carrez wrote: > Ed Leafe wrote: >> On Feb 10, 2017, at 2:48 PM, Matt Riedemann wrote: >> >>> I assumed we'd take the opportunity to talk about capabilities [1] at the >>> PTG but couldn't find any etherpad for the API WG on the wiki [2]. >>> >>> Is the API WG getting

Re: [openstack-dev] [telemetry] Pollsters for Veritas HyperScale

On 10/02/17 12:24 AM, Nirendra Awasthi wrote: > Overview: > * HyperScale pollsters are required to collect and monitor HyperScale > storage statistics. > * Collected statistics can be visualized in HyperScale dashboard. > * Pollsters are deployed on all the managed computes, HyperScale data >

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

On 2017-02-13 18:23:19 +0300 (+0300), Mikhail Fedosin wrote: [...] > Almost every project works with some binary data and must store it > somewhere, and almost always storage itself is not the part of the > project's mission. This issue has often been neglected. For this reason > there is no

Re: [openstack-dev] [tripleo] Blueprints for DPDK in OvS2.6

On Wed, Feb 8, 2017 at 1:59 AM, Saravanan KR wrote: > Hello, > > We have raised 2 BP for OvS2.6 integration with DPDK support. > > Basic Migration - > https://blueprints.launchpad.net/tripleo/+spec/ovs-2.6-dpdk (Targeted > for March) > OvS 2.6 Features - >

[openstack-dev] [puppet] Reminder meeting on Feb 14th @ 1500 UTC

Just a reminder but we will be having our meeting tomorrow Feb 14th at 1500 UTC in #openstack-meeting-4 unless the agenda[0] remains empty. So if you have something you wish to talk about it, please add it to the agenda. As always the the previous meeting logs and agendas are reviewable here[1].

Re: [openstack-dev] [governance][tc][rally] Rally (Re: [rally][release] How rally release version)

Andrey, My apologies. Thanks for the clarifications. -- Dims On Mon, Feb 13, 2017 at 10:27 AM, Andrey Kurilin wrote: > > > On Mon, Feb 13, 2017 at 4:49 PM, Davanum Srinivas wrote: >> >> Andrey, >> >> It's a question, not a proposal. > > > Sorry, but

[openstack-dev] [kolla] Debian support?

As part of my Linaro work I work on getting Debian in Kolla great again. Posted set of patches for review [1] which make it work properly. 1. https://review.openstack.org/#/q/owner:%22Marcin+Juszkiewicz Images are quite in sync with Ubuntu ones. There are some exceptions when builds are done

Re: [openstack-dev] [rally][ironic][release] How rally/ironic release version

This is right, we're release with the help of the release team and this repository. The files do not exist, because we haven't had any releases in Ocata for these projects yet (we're not milestone based). On 02/13/2017 04:27 PM, Jeffrey Zhang wrote: @Dmitry, thanks. So ironic will use

Re: [openstack-dev] [governance][tc][rally] Rally (Re: [rally][release] How rally release version)

On Mon, Feb 13, 2017 at 4:49 PM, Davanum Srinivas wrote: > Andrey, > > It's a question, not a proposal. > Sorry, but your message doesn't sound like a question. It sounds like a polite proposal. > If you don't do use releases repo, then rally information will be stale >

Re: [openstack-dev] [rally][ironic][release] How rally/ironic release version

@Dmitry, thanks. So ironic will use "openstack/releases" for release management? right? On Mon, Feb 13, 2017 at 11:19 PM, Dmitry Tantsur wrote: > We're still not done :( But we're very close! Please expect releases later > today or tomorrow. > > On 02/13/2017 04:09 PM,

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Hello! Let me quickly describe my vision of the problem. I asked this question to Brian last Friday, because it is evident that the projects have the intersection in functionality. For this reason, I proposed to bring Glare back and develop it as a new generation of Glance service. Perhaps such

Re: [openstack-dev] [rally][ironic][release] How rally/ironic release version

We're still not done :( But we're very close! Please expect releases later today or tomorrow. On 02/13/2017 04:09 PM, Jeffrey Zhang wrote: loop ironic tag in subject. i do not see any release info in Ocata cycle in ironic[0] and ironic-inspector[1] project. [0]

Re: [openstack-dev] [rally][ironic][release] How rally/ironic release version

loop ironic tag in subject. i do not see any release info in Ocata cycle in ironic[0] and ironic-inspector[1] project. [0] https://github.com/openstack/releases/blob/master/deliverables/ocata/ironic.yaml [1]

Re: [openstack-dev] [rally][release] How rally release version

To add, please consider appointing a CPL to coordinate the update to the releases/ repo: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management Thanks, Dims On Mon, Feb 13, 2017 at 9:15 AM, Doug Hellmann wrote: > Excerpts from Andrey Kurilin's message of

[openstack-dev] [all] [ptg] [goals] Pike WSGI Goal Planning

I created https://etherpad.openstack.org/p/ptg-pike-wsgi so we can start discussing on this goal. Thierry confirmed to me that we would have a room on either Monday or Tuesday. Please let us know in the etherpad if you have schedule constraints. Also, if you're PTL or / and interested by this

Re: [openstack-dev] [governance][tc][rally] Rally (Re: [rally][release] How rally release version)

Andrey, It's a question, not a proposal. If you don't do use releases repo, then rally information will be stale here: https://releases.openstack.org/ Here's why we have a release team and things we do: https://governance.openstack.org/tc/reference/projects/release-management.html

Re: [openstack-dev] [governance][tc][rally] Rally (Re: [rally][release] How rally release version)

On 13/02/2017 14:02, Davanum Srinivas wrote: > Andrey, Rally team, > > Do you want Rally to be dropped from Governance and Releases repository? > > Thanks, > Dims > While I think the info should be removed from releases if there is no useful data there, why the removal from governance? Rally has

[openstack-dev] [tripleo] CI Squad Meeting Summary (week 6)

As always, if these topics interest you and you want to contribute to the discussion, feel free to join the next meeting: Time: Thursdays, 15:30-16:30 UTC Place: https://bluejeans.com/4113567798/ Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting We had only about half

Re: [openstack-dev] [governance][tc][rally] Rally (Re: [rally][release] How rally release version)

Hi Dims! I do not want to say except question "why you are proposing to do that?". I tried to find any rules about releasing at https://governance.openstack.org, but I could not. Please point me what rule I broke. On Mon, Feb 13, 2017 at 3:57 PM, Davanum Srinivas wrote: >

Re: [openstack-dev] [rally][release] How rally release version

Excerpts from Andrey Kurilin's message of 2017-02-13 12:14:31 +0200: > Hi Jeffrey, > > Rally team do not use "releases" repo at all, that is why information at > [2] is outdated. > Our release workflow is making a proper tag and pushing it via Gerrit. I > find it more convenient. Please propose

Re: [openstack-dev] [fuel][kolla][kuryr][openstack-ansible][openstack-helm] OpenStack on containers leaveraging kuryr

Flavio, Somehow the fuel project and openstack-ansible project got left off the taglines. I’m not sure if the fuel peeps saw this thread, but I know the openstack-ansible peeps didn’t see the thread. As a result, I’ve added those taglines. Hopefully we can include the broader deployment

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

On 13/02/17 14:37 +0100, Thierry Carrez wrote: Brian Rosmaita wrote: I want to give all interested parties a heads up that I have scheduled a session in the Macon room from 9:30-10:30 a.m. on Thursday morning (February 23). [...] Thanks for setting this meeting up. I'll be there! Ditto! I'm

Re: [openstack-dev] [rally][release] How rally release version

On Mon, Feb 13, 2017 at 3:17 PM, Jeffrey Zhang wrote: > @Andrey, thanks for the explanation. > > The issue is: how can i know which tag works with certain OpenStack > branch? For example, which tag > works with OpenStack Ocata release? There is no place recording this. >

[openstack-dev] [governance][tc][rally] Rally (Re: [rally][release] How rally release version)

Andrey, Rally team, Do you want Rally to be dropped from Governance and Releases repository? Thanks, Dims On Mon, Feb 13, 2017 at 8:17 AM, Jeffrey Zhang wrote: > @Andrey, thanks for the explanation. > > The issue is: how can i know which tag works with certain

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

-Original Message- From: Clint Byrum Reply: OpenStack Development Mailing List (not for usage questions) Date: February 12, 2017 at 20:09:04 To: openstack-dev Subject:  Re: [openstack-dev]

Re: [openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

Brian Rosmaita wrote: > I want to give all interested parties a heads up that I have scheduled a > session in the Macon room from 9:30-10:30 a.m. on Thursday morning > (February 23). > [...] Thanks for setting this meeting up. I'll be there! -- Thierry Carrez (ttx)

Re: [openstack-dev] [tripleo] A sneak peek to TripleO + Containers

On 13/02/17 08:19 -0500, Emilien Macchi wrote: On Mon, Feb 13, 2017 at 5:46 AM, Flavio Percoco wrote: Hello, I've been playing with a self-installing container for the containerized TripleO undercloud and I thought I'd share some of the progress we've made so far. This is

Re: [openstack-dev] [api] API WG PTG planning

Ed Leafe wrote: > On Feb 10, 2017, at 2:48 PM, Matt Riedemann wrote: > >> I assumed we'd take the opportunity to talk about capabilities [1] at the >> PTG but couldn't find any etherpad for the API WG on the wiki [2]. >> >> Is the API WG getting together on Monday or

Re: [openstack-dev] [tripleo] A sneak peek to TripleO + Containers

On Mon, Feb 13, 2017 at 5:46 AM, Flavio Percoco wrote: > Hello, > > I've been playing with a self-installing container for the containerized > TripleO > undercloud and I thought I'd share some of the progress we've made so far. > > This is definitely not at its final, ideal,

Re: [openstack-dev] [rally][release] How rally release version

@Andrey, thanks for the explanation. The issue is: how can i know which tag works with certain OpenStack branch? For example, which tag works with OpenStack Ocata release? There is no place recording this. I also found there are some other project do not use "project/releases" project. May they

[openstack-dev] [tripleo] PTG sessions - agenda is drafted! (action required)

If you plan to attend TripleO sessions in Atlanta, please review the first draft of our schedule: https://etherpad.openstack.org/p/tripleo-ptg-pike Please let me know ASAP if we need to move a session or if there is some important overlap. I'll let chairs to prepare a blueprint / etherpad / some

Re: [openstack-dev] nova-docker deleted from github

Debdipta, github is merely a mirror. Over the last 2 years, multiple messages have gone to -dev@ and -operators@ mailing list about nova-docker not having a core team and that we needed one to keep it going. So we had to shutdown the shop on it:

Re: [openstack-dev] nova-docker deleted from github

Debdipta, github is merely a mirror. Over the last 2 years, multiple messages have gone to -dev@ and -operators@ mailing list about nova-docker not having a core team and that we needed one to keep it going. So we had to shutdown the shop on it:

Re: [openstack-dev] [heat][tripleo][mistral][all]PTG: Cross-Project: OpenStack Orchestration Integration

On Mon, Feb 13, 2017 at 4:48 AM, Rico Lin wrote: > Dear all > > PTG is approaching, we have few ideas around TripleO team ([1] and [2]) > about use case like using Mistral through Heat. It seems some great > OpenStacker already start thing about how the Orchestration

Re: [openstack-dev] [Designate] In what sense is it multi-tenant?

On 10/02/17 21:51, Mike Spreitzer wrote: > In what sense is Designate multi-tenant? Can it be programmed to give > different views to different DNS clients? (If so, how?) > > Thanks, > Mike It is multi-tenant as it allows multiple users to use the same DNS infra, while keeping control of DNS

Re: [openstack-dev] [tripleo] A sneak peek to TripleO + Containers

On 13/02/17 11:46 +0100, Flavio Percoco wrote: Hello, I've been playing with a self-installing container for the containerized TripleO undercloud and I thought I'd share some of the progress we've made so far. This is definitely not at its final, ideal, state but I wanted to provide a sneak

[openstack-dev] [tripleo] A sneak peek to TripleO + Containers

Hello, I've been playing with a self-installing container for the containerized TripleO undercloud and I thought I'd share some of the progress we've made so far. This is definitely not at its final, ideal, state but I wanted to provide a sneak peek to what is coming and what the

[openstack-dev] [heat][magnum][murano][sahara][tripleo][mistral][all]PTG: Cross-Project:Orchestration feedback and announcement

Dear all We would like to have a Cross Project fishbowl session about Orchestration feedback and announcement. We would like to help on any improvement that will potentially help other projects. That's why we need your feedback. Heat has landed some cool improvement like reduce 60% of memory

Re: [openstack-dev] [monasca] Ideas to work on

Hi, Here the URL to monasca-log-api documentation [1]. Cheers Witek [1] https://github.com/openstack/monasca-log-api/tree/master/documentation I would like to look at logs publishing as well. But unfortunately I did not find the monasca-log-api doc, which is supposed to be at

Re: [openstack-dev] [rally][release] How rally release version

Hi Jeffrey, Rally team do not use "releases" repo at all, that is why information at [2] is outdated. Our release workflow is making a proper tag and pushing it via Gerrit. I find it more convenient. On Mon, Feb 13, 2017 at 9:13 AM, Jeffrey Zhang wrote: > Hey guys, >

  1   2   >