Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Mon, Jul 10, 2017 at 11:33:51AM +, Gary Kotton wrote: > Hi, > Will this also be moving to eol - > https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt? We need to be very careful EOLing that repo (if at all) as project have deep links to the

Re: [openstack-dev] [kuryr] Subnet pool does not exist error

Thanks Liping. FYI, I use Docker version 17.06.0-ce. $ docker --version Docker version 17.06.0-ce, build 02c1d87 Hyunsun > On 12 Jul 2017, at 1:51 PM, Liping Mao (limao) wrote: > > Hi Hyunsun, > > From you log: > 2017-07-11 09:21:20.221 12 ERROR kuryr_libnetwork.utils [-]

Re: [openstack-dev] [zun] sandbox and clearcontainers

Hi Surya, Please see my response inline. Currently Zun have two drivers for managing containers: Docker and NovaDocker. Sandbox was initially implemented for the NovaDocker driver which we are going to deprecate soon. Also we are working on making the sandbox optional for the Docker driver. See

Re: [openstack-dev] [kuryr] Subnet pool does not exist error

Hi Hyunsun, From you log: 2017-07-11 09:21:20.221 12 ERROR kuryr_libnetwork.utils [-] Unexpected error happened: Subnet with pool f96b5ff6-4065-4eed-9854-3a54122f90c9 does not exist.: KuryrException: Subnet with pool f96b5ff6-4065-4eed-9854-3a54122f90c9 does not exist. It looks like failed

Re: [openstack-dev] [zun] sandbox and clearcontainers

Hi Surya, First, I would like to provide some context for folks who are not familiar with the sandbox concept in Zun. The "sandbox" is for providing isolated environment for one or multiple containers. In docker driver, we used it as a placeholder of a set of Linux namespaces (i.e. network,

Re: [openstack-dev] [mistral] CloudFlow demo available online

Thanks Guy! Great work ) Renat Akhmerov @Nokia On 11 Jul 2017, 16:53 +0700, Dougal Matthews , wrote: > Thanks for this - it is really useful to be able to click around and play > with the UI - gives me a much better feel for it. > > > > On 11 July 2017 at 08:26, Shaanan, Guy

Re: [openstack-dev] [kuryr] Subnet pool does not exist error

Here it is. $ cat /etc/kuryr/kuryr.conf [DEFAULT] bindir = /usr/libexec/kuryr capability_scope = global log_dir = /var/log/kuryr log_file = kuryr.log [neutron] project_name = admin username = admin password = nova auth_url = http://10.1.1.161:35357/v2.0 auth_type = password Hyunsun > On 12

Re: [openstack-dev] [kuryr] Subnet pool does not exist error

Can you help to attach your kuryr.conf configuration file? Regards, Liping Mao 发件人: Hyunsun Moon 答复: OpenStack List 日期: 2017年7月12日 星期三 09:44 至: OpenStack List 主题: [openstack-dev] [kuryr] Subnet pool

Re: [openstack-dev] [keystone] office hours report 2017-7-7

Hi, So this email is relevant to my interests as an operator. =) On Tue, Jul 11, 2017 at 9:35 PM, Lance Bragstad wrote: > *The future of the templated catalog backend* > > Some issues were uncovered, or just resurfaced, with the templated catalog > backend. The net of the

Re: [openstack-dev] [nova] Should PUT /os-services be idempotent?

2017-07-12 9:18 GMT+08:00 Matt Riedemann : > I'm looking for some broader input on something being discussed in this > change: > > https://review.openstack.org/#/c/464280/21/nova/api/openstac > k/compute/services.py > > This is collapsing the following APIs into a single API:

Re: [openstack-dev] [heat] Online video meet up this week (topic:review)

2017-07-12 2:10 GMT+08:00 Jeremy Stanley : > > On 2017-07-12 01:47:02 +0800 (+0800), Rico Lin wrote: > [...] > > we will make our meeting this week as an online video meeting > [...] > > Friendly reminder: "If the project has meetings [...] they should be > public and in IRC.

Re: [openstack-dev] [nova] Should PUT /os-services be idempotent?

On Jul 11, 2017, at 8:18 PM, Matt Riedemann wrote: > With the old APIs, if you tried to enable and already enabled service, it was > not an error. The same is you tried to disable an already disabled service. > It doesn't change anything, but it's not an error. > > The

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Wed, Jul 12, 2017 at 11:47 AM, James Slagle wrote: > On Tue, Jul 11, 2017 at 6:53 PM, Steve Baker wrote: > > > > > > On Tue, Jul 11, 2017 at 6:51 AM, James Slagle > > wrote: > >> > >> On Mon, Jul 10, 2017 at 11:37 AM, Lars

Re: [openstack-dev] [tripleo][ci] decreased coverage for telemetry

On Tue, Jul 11, 2017 at 9:04 PM, Emilien Macchi wrote: > On Tue, Jul 11, 2017 at 12:41 PM, Pradeep Kilambi wrote: > > On Tue, Jul 11, 2017 at 3:17 PM, Wesley Hayutin > wrote: > >> Greetings, > >> > >> I was looking through the mailing

[openstack-dev] [kuryr] Subnet pool does not exist error

Hi all, I’m getting an exception when creating a service with Kuryr network. I created and installed kuryr plugin by building plugin rootfs from the source code. Here’s what I did after that. $ sudo docker network create --driver=kuryr/libnetwork2:latest --ipam-driver=kuryr/libnetwork2:latest

[openstack-dev] [keystone] office hours report 2017-7-7

Hey all, This is a summary of what was worked on today during office hours. Full logs of the meeting can be found below: http://eavesdrop.openstack.org/meetings/office_hours/2017/office_hours.2017-07-11-19.00.log.html *The future of the templated catalog backend * Some issues were uncovered,

[openstack-dev] [nova] Should PUT /os-services be idempotent?

I'm looking for some broader input on something being discussed in this change: https://review.openstack.org/#/c/464280/21/nova/api/openstack/compute/services.py This is collapsing the following APIs into a single API: Old: * PUT /os-services/enable * PUT /os-services/disable * PUT

[openstack-dev] [all] [tc] Technical Committee office hours is starting now on #openstack-tc!

Join #openstack-tc if you would like to discuss with TC members, we're online and happy to answer any question or discuss about any topic. Thanks, -- Emilien Macchi __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tripleo][ci] decreased coverage for telemetry

On Tue, Jul 11, 2017 at 12:41 PM, Pradeep Kilambi wrote: > On Tue, Jul 11, 2017 at 3:17 PM, Wesley Hayutin wrote: >> Greetings, >> >> I was looking through the mailing list and I did not see any emails >> explicitly calling out the decreased coverage for

Re: [openstack-dev] [tripleo][ci] decreased coverage for telemetry

On Tue, Jul 11, 2017 at 3:41 PM, Pradeep Kilambi wrote: > On Tue, Jul 11, 2017 at 3:17 PM, Wesley Hayutin > wrote: > > Greetings, > > > > I was looking through the mailing list and I did not see any emails > > explicitly calling out the decreased coverage

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

On 07/11/2017 06:47 AM, Flavio Percoco wrote: On 11/07/17 14:20 +0300, Mikhail Fedosin wrote: On Tue, Jul 11, 2017 at 1:43 AM, Monty Taylor wrote: On 07/10/2017 04:31 PM, Mikhail Fedosin wrote: Third, all these changes can be hidden in Glare client. So if we try a

Re: [openstack-dev] TR: [tricircle]

Hi Meher, Yes, as Victor pointed out, it should be done by the devstack script. But in our daily development, I use (maybe most of us) Ubuntu to install Tricircle through devstack, so not sure whether there is some bug under RHEL, and I have no RHEL distribution. Best Regards Chaoyi Huang

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 5:53 PM, Steve Baker wrote: > > > On Tue, Jul 11, 2017 at 3:37 AM, Lars Kellogg-Stedman > wrote: >> >> On Fri, Jul 7, 2017 at 1:50 PM, James Slagle >> wrote: >>> >>> There are also some ideas forming around

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 6:53 PM, Steve Baker wrote: > > > On Tue, Jul 11, 2017 at 6:51 AM, James Slagle > wrote: >> >> On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman >> wrote: >> > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle

[openstack-dev] [zun] sandbox and clearcontainers

Dell - Internal Use - Confidential Hi Folks, I am just trying to wrap my head around zun's sandboxing and clear containers. From what Hongbin told in Barcelona ( see the attached pic which I scrapped from his video) [cid:image001.jpg@01D2FAA3.AE2FD7F0] current implementation in Zun

Re: [openstack-dev] [tc] [all] TC Report 28

On 2017-07-11 23:25:40 +0100 (+0100), Chris Dent wrote: [...] > ## "big tent" and "hosted projects" [...] > Does anyone recall where this topic landed, or if it hasn't yet > landed, does anyone have good ideas on how to get it to land? My favorite responses gravitated toward (paraphrasing, and

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 6:51 AM, James Slagle wrote: > On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman > wrote: > > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle > wrote: > >> > >> There are also some ideas forming around

Re: [openstack-dev] [nova] bug triage experimentation

On 2017-07-10 07:33:28 -0400 (-0400), Sean Dague wrote: [...] > Ideally storyboard would just be a lot more receptive to these kinds of > things, by emitting a more native event stream, Well, there is

[openstack-dev] [tc] [all] TC Report 28

Blog version at: https://anticdent.org/tc-report-28.html It's been a while since I've done one of these. I was between employers and taking a break but am now back in the groove. There's been some activity in the interim, which I'll try to summarize below, but first notes from this evening's

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 3:37 AM, Lars Kellogg-Stedman wrote: > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle > wrote: > >> There are also some ideas forming around pulling the Ansible playbooks >> > and vars out of Heat so that they can be rerun (or run

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

> can't speak regarding ceilometer-powervm since it's vendor specific. I can confirm that ceilometer-powervm (and nova-powervm and networking-powervm) shouldn't be tracked with this effort, since they publish to readthedocs and not docs.openstack.org. Something something Big Tent something

[openstack-dev] [all][docs] using openstackdocstheme

As projects review patches related to the migration project, please keep in mind that only *official* projects listed as being under TC governance [1] should use the openstackdocs theme. If your documentation is not being published to docs.openstack.org, please use a different theme. Doug [1]

[openstack-dev] [octavia] Webex to discuss Octavia L3 active/active spec Part II

This is part II of the discussion around the L3 active/active spec (https://review.openstack.org/#/c/453005/). The goal of this meeting is to get community feedback in order to finalize the details around the L3 active/active spec. I have posted the meeting details below. Date & Time: July

Re: [openstack-dev] [nova] bug triage experimentation

Sean Dague writes: > On 07/05/2017 03:23 PM, Emilien Macchi wrote: > >> >> I also believe that some of the scripts could be transformed into >> native features of Storyboard where bugs could be auto-triaged >> periodically without human intervention. >> Maybe it would convince

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

On 11/07/17 10:43 AM, Doug Hellmann wrote: > Excerpts from gordon chung's message of 2017-07-11 14:23:41 +: >> >> On 10/07/17 01:26 PM, Doug Hellmann wrote: >>> openstack/ceilometer-powervm >>> openstack/ceilometermiddleware >> >> i don't believe there are docs for these.

Re: [openstack-dev] [tripleo][ci] decreased coverage for telemetry

On Tue, Jul 11, 2017 at 3:17 PM, Wesley Hayutin wrote: > Greetings, > > I was looking through the mailing list and I did not see any emails > explicitly calling out the decreased coverage for telemetry in tripleo due > to [1]. A series of changes went into the CI system to

Re: [openstack-dev] [tc] Status update, July 7th

On 07/11/2017 12:14 PM, Dean Troyer wrote: On Fri, Jul 7, 2017 at 3:19 AM, Thierry Carrez wrote: == Need for a TC meeting next Tuesday == [...] others). Who is up for discussing those items at our usual meeting slot time on Tuesday ? I am unlikely to make the

Re: [openstack-dev] [keystone] deprecating and removing tools/sample_data.sh

Good point. I did a bit more digging and it looks like it was originally intended for devstack [0]. At least based on the original commit message that introduced the file. Devstack seems to take its own approach to generating sample data, mainly using keystone-manage and functions defined in

[openstack-dev] [tripleo][ci] decreased coverage for telemetry

Greetings, I was looking through the mailing list and I did not see any emails explicitly calling out the decreased coverage for telemetry in tripleo due to [1]. A series of changes went into the CI system to disable telemetry [2]. There is work being done to restore more coverage for telemetry

Re: [openstack-dev] [zun] Some general ZUN use case / drivers type questions

Greg, No, it isn’t. We are working hard to integrate with Cinder (either via Fuxi or direct integration). Perhaps this design spec can provide some information about where we are heading to: https://review.openstack.org/#/c/468658/ . Best regards, Hongbin From: Waines, Greg

Re: [openstack-dev] [oslo] scheduling oslosphinx for retirement at the start of queens

+1 On 07/10/2017 08:10 AM, Doug Hellmann wrote: Oslo team, With all documentation now moving to use the openstackdocs theme, I propose that we retire the oslosphinx repository during Queens. We should go ahead and create the stable/pike branch at the end of this cycle, so that we have a way to

Re: [openstack-dev] [zun] Some general ZUN use case / drivers type questions

Thanks Hongbin, another quick question, is ZUN integrated with FUXI for Container mounting of Cinder Volumes yet ? ( my guess is no ... don’t see any options for that in the zun cli for create or run ) Greg. From: Hongbin Lu Date: Tuesday, July 11, 2017 at 2:04 PM To:

Re: [openstack-dev] [heat] Online video meet up this week (topic:review)

On 2017-07-12 01:47:02 +0800 (+0800), Rico Lin wrote: [...] > we will make our meeting this week as an online video meeting [...] Friendly reminder: "If the project has meetings [...] they should be public and in IRC. They should all be logged and published"

Re: [openstack-dev] [TripleO] Migration from Neutron ML2OVS to OVN

On 07/11/2017 10:17 AM, Numan Siddique wrote: Hello Tripleo team, I have few questios regarding migration from neutron ML2OVS to OVN. Below are some of the requirements - We want to migrate an existing depoyment from Neutroon default ML2OVS to OVN - We are targetting this for tripleo

Re: [openstack-dev] [zun] Some general ZUN use case / drivers type questions

Hi Greg, There is no such API in Zun. I created a BP for this feature request: https://blueprints.launchpad.net/zun/+spec/show-container-engine-info . Hopefully, the implementation will be available at the next release or two. Best regards, Hongbin From: Waines, Greg

[openstack-dev] [heat] Online video meet up this week (topic:review)

Hi Team We would like to start doing video online meetup and see if we can all reach better co-work with that. The reason for doing this is because we're a global team which almost impossible for all of us to literally sit in the same room in PTG/anywhere (it's just not possible to ask all

Re: [openstack-dev] [tc] Status update, July 7th

On Fri, Jul 7, 2017 at 3:19 AM, Thierry Carrez wrote: > == Need for a TC meeting next Tuesday == [...] > others). Who is up for discussing those items at our usual meeting slot > time on Tuesday ? I am unlikely to make the meeting, travel plans are more fluid than I would

Re: [openstack-dev] TR: [tricircle]

Hi Meher, I don’t think that you need to create those folders or at least that it’s shown in the devstack functions[1]. Regards/Saludos Victor Morales [1] https://github.com/openstack-dev/devstack/blob/master/lib/apache#L178-L192 From: "meher.h...@orange.com" Reply-To:

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

Excerpts from Akihiro Motoki's message of 2017-07-11 23:56:30 +0900: > Thanks for update the status! > > > openstack/networking-midonet > > The doc-migration work networking-midonet has almost completed. > Unfortunately they do not use 'doc-migration' topic as it seems they > already started >

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

On 2017-07-11 23:56:30 +0900 (+0900), Akihiro Motoki wrote: > 2017-07-11 2:26 GMT+09:00 Doug Hellmann : [...] > > openstack/networking-vsphere [...] > This is not a project under the TC governance. And as such, also seems to correctly not be publishing any documentation on

Re: [openstack-dev] [keystone] We still have a not identical HEAD response

On Tue, Jul 11, 2017 at 12:06 PM Attila Fazekas wrote: > Hi all, > > Long time ago it was discussed to make the keystone HEAD responses > right [1] as the RFC [2][3] recommends: > > " A response to the HEAD method is identical to what an equivalent >request made with a

[openstack-dev] [TripleO] Migration from Neutron ML2OVS to OVN

Hello Tripleo team, I have few questios regarding migration from neutron ML2OVS to OVN. Below are some of the requirements - We want to migrate an existing depoyment from Neutroon default ML2OVS to OVN - We are targetting this for tripleo Queen's release. - The plan is to first upgrade the

[openstack-dev] [keystone] office hours reminder

Hey all, Just a quick reminder that today we will be holding office hours after the keystone meeting [0]. See you there! Thanks, Lance [0] http://eavesdrop.openstack.org/#Keystone_Team_Meeting signature.asc Description: OpenPGP digital signature

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

Thanks for update the status! > openstack/networking-midonet The doc-migration work networking-midonet has almost completed. Unfortunately they do not use 'doc-migration' topic as it seems they already started the document overhaul before the doc-migration starts.

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

Excerpts from gordon chung's message of 2017-07-11 14:23:41 +: > > On 10/07/17 01:26 PM, Doug Hellmann wrote: > > openstack/ceilometer-powervm > > openstack/ceilometermiddleware > > i don't believe there are docs for these. ceilometermiddleware is a > simple wsgi middleware and it's usage

Re: [openstack-dev] [kolla] failed to download image from TryStack

On 2017-07-11 17:24:55 +0800 (+0800), Jeffrey Zhang wrote: [...] > first of all, this site is not trystack, it is tarballs.openstack.org. > > I asked openstack infra team. got following feedback > > > this was disabled yesterday since the images produced massive > > load. fungi started putting

Re: [openstack-dev] [zun] Some general ZUN use case / drivers type questions

Hey Hongbin, is there a way to display ZUN’s resource usage ? i.e. analogous to nova’s “nova hypervisor-show ” e.g. memory usages, cpu usage, etc . Greg. From: Hongbin Lu Date: Friday, July 7, 2017 at 2:08 PM To: Greg Waines ,

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

Excerpts from Renat Akhmerov's message of 2017-07-11 12:08:23 +0700: > On 11 Jul 2017, 00:27 +0700, wrote: > > > openstack/mistral-dashboard > > openstack/mistral-extra > > These two are not supposed to have docs at all. We should probably just > remove the “doc” folder and corresponding CI

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

On 10/07/17 01:26 PM, Doug Hellmann wrote: > openstack/ceilometer-powervm > openstack/ceilometermiddleware i don't believe there are docs for these. ceilometermiddleware is a simple wsgi middleware and it's usage is part of ceilometer's install docs. ceilometer-powervm contains the powervm

Re: [openstack-dev] [Glare][TC][Interop] Application for inclusion of Glare in the list of official projects

On 2017-07-11 13:47:41 +0200 (+0200), Flavio Percoco wrote: [...] > Anything that delays the transition to the new thing is providing > a fake bridge to the users. It's a bridge that will be blown-up > eventually. > > To make a hypothetical transition from Glance to Glare works > smoothly, we

[openstack-dev] [TripleO][UI][UX] Improving the Tag Nodes and Assign Nodes to Roles workflow

Hi All, I'm trying out a new way of sharing design proposals based on user feedback and I've put together a presentation showing an area of improvement in the TripleO UI along with my suggestions moving forward. I'd love to have a discussion on this and continue to make the proposal even better

Re: [openstack-dev] [keystone] We still have a not identical HEAD response

Based on the comments and opinions in the original thread, I think a fix for this is justified. I wouldn't mind running this by the TC to double check that nothing has changed from the first time we had to fix this issue though. On 07/11/2017 06:03 AM, Attila Fazekas wrote: > Hi all, > > Long

[openstack-dev] TR: [tricircle]

[Logo Orange] Meher Hihi Intern ORANGE/IMT/OLN/WTC/CMA/MAX Fixe : +33 2 96 07 03

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

++ As I was not sure how to word it without sounding too opinionated without appropriate technical jargon. When most folks hear "mostly the same" regarding a critical component, and sometimes not so critical ones, that raises all kinds of red flags. I could not think from purely code aspect of

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

On 11/07/17 14:20 +0300, Mikhail Fedosin wrote: On Tue, Jul 11, 2017 at 1:43 AM, Monty Taylor wrote: On 07/10/2017 04:31 PM, Mikhail Fedosin wrote: Third, all these changes can be hidden in Glare client. So if we try a little, we can achieve 100% compatibility there,

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

On Tue, Jul 11, 2017 at 7:33 AM, Chris Dent wrote: > On Tue, 11 Jul 2017, Mikhail Fedosin wrote: > >> For example, deactivating an image in Glance looks like *POST* >> /v2/images/{image_id}/actions/deactivate with empty body. >> At one time, Chris Dent advised us to avoid

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

On Tue, 11 Jul 2017, Mikhail Fedosin wrote: For example, deactivating an image in Glance looks like *POST* /v2/images/{image_id}/actions/deactivate with empty body. At one time, Chris Dent advised us to avoid such decisions, and simply change the status of the artifact to 'deactivated' using

[openstack-dev] [fuxi] [kuryr] [stackube] [openstack-helm] [kolla-kubernetes] [magnum] [zun] Projects in the intersection of Kubernetes and OpenStack

Folks, Between the projects listed, we seem to be covering a whole lot of use cases. Are there others that we are missing? Anyone have other ideas for things we could be doing that needs a home? Thanks, Dims -- Davanum Srinivas :: https://twitter.com/dims

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

On Tue, Jul 11, 2017 at 1:43 AM, Monty Taylor wrote: > On 07/10/2017 04:31 PM, Mikhail Fedosin wrote: > >> Thank you for asking this! It's really very important and interesting, so >> I'm going to explain those things more detailed. >> >> First, when we designed Glare, we

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

On Tue, Jul 11, 2017 at 12:31 AM, Monty Taylor wrote: > On 07/10/2017 01:21 PM, Ed Leafe wrote: > >> On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin mfedo...@gmail.com>> wrote: >> >> Given all the advantages and features of Glare, I believe that it can

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

On Tue, Jul 11, 2017 at 12:54 AM, Monty Taylor wrote: > On 07/10/2017 04:31 PM, Monty Taylor wrote: > >> On 07/10/2017 01:21 PM, Ed Leafe wrote: >> >>> On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin >> > wrote: >>> >>> Given all

[openstack-dev] [keystone] We still have a not identical HEAD response

Hi all, Long time ago it was discussed to make the keystone HEAD responses right [1] as the RFC [2][3] recommends: " A response to the HEAD method is identical to what an equivalent request made with a GET would have been, except it lacks a body. " So, the status code needs to be identical

[openstack-dev] [neutron] No CCF meeting

Hi all, The repository has been updated to pass the gate: https://review.openstack.org/#/c/480199/. There will be no meeting today as we have no outstanding topics to discuss and are still working on submitting the first round of code of the Common Classification Framework, which is due for

Re: [openstack-dev] [kolla] why common_options type is dictionary ?

If I modify kolla_docker.py , how to debug an ansible module ? I find http://docs.ansible.com/ansible/dev_guide/developing_modules.html, but failed to run it as following. how do you do testing when develop the module ? [root@server120 ansible-module]# ansible/hacking/test-module -m

Re: [openstack-dev] 回复： [devstack] How to start all OpenStack servicesafter restarting system?

I believe screen is no longer the system to manage services in DevStack, but systemd is now: https://docs.openstack.org/devstack/latest/systemd.html You should just use systemctl to bring up all OpenStack services. HTH 2017-07-11 11:40 GMT+02:00 zhi : > Hi, Abhishek. >

Re: [openstack-dev] [kolla] why common_options type is dictionary ?

Ok, I see. I wanted to add "--ulimit " parameter when docker run , It seems that I have to add an extra parameter for kolla_docker module in kolla_docker.py. On 7/11 17:08, Jeffrey Zhang wrote: there are lots of non-plain variables in kolla, dict or list in Ansible. if you do not want to

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

Hi Ifat, Thank you for investigating the issue. The port name is unique on the graph. The ovs port name in collectd ovs_events plugin is identified by the ‘plugin_instance’ notification field. Thanks and Regards, Volodymyr From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]

Re: [openstack-dev] [mistral] CloudFlow demo available online

Thanks for this - it is really useful to be able to click around and play with the UI - gives me a much better feel for it. On 11 July 2017 at 08:26, Shaanan, Guy (Nokia - IL/Kfar Sava) < guy.shaa...@nokia.com> wrote: > CloudFlow (the Mistral Workflow Visualization Tool) demo is now available >

Re: [openstack-dev] 回复： [devstack] How to start all OpenStack servicesafter restarting system?

Hi, Abhishek. I have a question about devstack. The file "stack-screenrc" doesn't exist when I installed devstack successfully, why? I find all over the devstack directory but I can not find it. Could you give me some advice? Thanks Zhi Chang 2016-08-22 16:42 GMT+08:00 wk <304702...@qq.com>:

Re: [openstack-dev] [kolla] failed to download image from TryStack

first of all, this site is not trystack, it is tarballs.openstack.org. I asked openstack infra team. got following feedback > this was disabled yesterday since the images produced massive load. fungi started putting up a caching proxy for these. This is disabled and will be enabled in the

Re: [openstack-dev] [kolla] why common_options type is dictionary ?

there are lots of non-plain variables in kolla, dict or list in Ansible. if you do not want to override the dict, you can add following into globals.yml file. docker_common_options: auth_email: "{{ docker_registry_email }}" auth_password: "{{ docker_registry_password }}"

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

Hi Volodymyr, I’m working on this issue. One question: is the port name, as defined by ‘plugin_instance’, supposed to be unique in the graph? If not, then how do you uniquely identify the port (in collectd)? Thanks, Ifat. From: "Mytnyk, VolodymyrX" Reply-To:

Re: [openstack-dev]  [kolla][kolla-ansible] ceph_osd error when startup ceph_osd container.

Hi, This usually means your ceph mons have failed to cluster correctly. The osd bootstrap calls 'ceph quorum_status' to ensure a successful quorum before proceeding. If the mons are blocked or otherwise unavailable this command can time out which is likely what you're seeing. Make sure the

Re: [openstack-dev] [kolla] why common_options type is dictionary ?

Because its a series of key value pairs: https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L96-L105 Is there another type you feel would fit better? On 11/07/17 05:22, Margin Hu wrote: Hi Guys: I want to set docker_common_options parameter but find its type is

[openstack-dev] [masakari]Remove ERROR instances from recovery targets

Hello all, Current Masakari also rescues ERROR instances when host failure happen. Those instances will be changed to ACTIVE after rescued.[1] But I think that some users don't want to rescue ERROR instances. For example, if user is running 1ACT/n SBY application on instances, launching ERROR

[openstack-dev] [mistral] CloudFlow demo available online

CloudFlow (the Mistral Workflow Visualization Tool) demo is now available online[1] using a real Mistral Pike instance. You can evaluate the tool by selecting one of the pre-existing executions, and: * See it's YAML definition, * Watch the execution information, * Select a task and