[openstack-dev] [octavia] Some tips about amphora driver

Recently, my team plans to provider load balancing services with octavia.I recorded some of the needs and suggestions of our team members.The following suggestions about amphora may be very useful. [1] User can specify image and flavor for amphora. [2] Enable multi processes(version<1.8) or multi

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

On Fri, 06 Jul 2018 11:30:15 +0900 Alex Xu wrote > > > 2018-07-06 10:03 GMT+08:00 Alex Xu : > > > 2018-07-06 2:55 GMT+08:00 melanie witt : > +openstack-dev@ > > On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: > But, I can not use nova command, endpoint

[openstack-dev] [masakari] Introspective Instance Monitoring through QEMU Guest Agent

Thanks Tushar Patil for the +1 for 547118. In regards of the following review: https://review.openstack.org/#/c/534958/ Any more comment? Thanks. Louie From: Tushar Patil (Code Review) [rev...@openstack.org] Sent: Tuesday, July 03, 2018 8:48 PM To: Kwan,

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

2018-07-06 10:03 GMT+08:00 Alex Xu : > > > 2018-07-06 2:55 GMT+08:00 melanie witt : > >> +openstack-dev@ >> >> On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: >> >>> But, I can not use nova command, endpoint nova have been redirected from https to http.

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

2018-07-06 2:55 GMT+08:00 melanie witt : > +openstack-dev@ > > On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: > >> But, I can not use nova command, endpoint nova have been redirected from >>> https to http. Here:http://prntscr.com/k2e8s6 (command: nova –insecure >>> service list) >>>

[openstack-dev] [python3][tc][infra][docs] changing the documentation build PTI to use tox

I have a governance patch up [1] to change the project-testing-interface (PTI) for building documentation to restore the use of tox. We originally changed away from tox because we wanted to have a single standard command that anyone could use to build the documentation for a project. It turns out

Re: [openstack-dev] [tc] [all] TC Report 18-26

Interesting. Thanks for the link. :) There is a lot of stuff there, so not sure it covers the part I'm talking about without more review. but if it doesn't it would be pretty easy to add by the looks of it. Kevin From: Jeremy Stanley [fu...@yuggoth.org]

Re: [openstack-dev] [tc] [all] TC Report 18-26

I use RDO in production. Its pretty far from RedHat OpenStack. though its been a while since I tried the TripleO part of RDO. Is it pretty well integrated now? Similar to RedHat OpenStack? or is it more Fedora like then CentOS like? Thanks, Kevin From: Dmitry

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

On 07/05/2018 01:55 PM, melanie witt wrote: +openstack-dev@ On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: But, I can not use nova command, endpoint nova have been redirected from https to http. Here:http://prntscr.com/k2e8s6  (command: nova –insecure service list) First of all, it

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

+openstack-dev@ On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: But, I can not use nova command, endpoint nova have been redirected from https to http. Here:http://prntscr.com/k2e8s6 (command: nova –insecure service list) First of all, it seems that the nova client is hitting /v2.1

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: > > I would almost rather see us organize the directories by service > name/project instead of implementation. > > Instead of: > > puppet/services/nova-api.yaml > puppet/services/nova-conductor.yaml > docker/services/nova-api.yaml >

Re: [openstack-dev] [tc] [all] TC Report 18-26

On Thu, Jul 5, 2018, 19:31 Fox, Kevin M wrote: > We're pretty far into a tangent... > > /me shrugs. I've done it. It can work. > > Some things your right. deploying k8s is more work then deploying ansible. > But what I said depends on context. If your goal is to deploy k8s/manage > k8s then

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, Jul 5, 2018 at 1:50 PM, Dan Prince wrote: > Last week I was tinkering with my docker configuration a bit and was a > bit surprised that puppet/services/docker.yaml no longer used puppet to > configure the docker daemon. It now uses Ansible [1] which is very cool > but brings up the

[openstack-dev] [TripleO] easily identifying how services are configured

Last week I was tinkering with my docker configuration a bit and was a bit surprised that puppet/services/docker.yaml no longer used puppet to configure the docker daemon. It now uses Ansible [1] which is very cool but brings up the question of how should we clearly indicate to developers and

Re: [openstack-dev] [tc] [all] TC Report 18-26

On 2018-07-05 17:30:23 + (+), Fox, Kevin M wrote: [...] > Deploying k8s doesn't need a general solution to deploying generic > base OS's. Just enough OS to deploy K8s and then deploy everything > on top in containers. Deploying a seed k8s with minikube is pretty > trivial. I'm not

Re: [openstack-dev] [tc] [all] TC Report 18-26

We're pretty far into a tangent... /me shrugs. I've done it. It can work. Some things your right. deploying k8s is more work then deploying ansible. But what I said depends on context. If your goal is to deploy k8s/manage k8s then having to learn how to use k8s is not a big ask. adding a

Re: [openstack-dev] [cinder][security][api-wg] Adding http security headers

Excerpts from Jim Rollenhagen's message of 2018-07-05 12:53:34 -0400: > On Thu, Jul 5, 2018 at 12:40 PM, Nishant Kumar E < > nishant.e.ku...@ericsson.com> wrote: > > > Hi, > > > > > > > > I have registered a blueprint for adding http security headers - > >

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, At today's meeting we discussed an issue that came up on a nova/placement review [9] wherein there was some indecision about whether a response code of 400 or 404 is more appropriate when a path segement expects a UUID, the request doesn't supply something that

Re: [openstack-dev] [cinder][security][api-wg] Adding http security headers

On Thu, Jul 5, 2018 at 12:40 PM, Nishant Kumar E < nishant.e.ku...@ericsson.com> wrote: > Hi, > > > > I have registered a blueprint for adding http security headers - > https://blueprints.launchpad.net/cinder/+spec/http-security-headers > > > > Reason for introducing this change - I work for AT

[openstack-dev] [oslo] Reminder about Oslo feature freeze

Hi, This is just a reminder that Oslo observes feature freeze earlier than other projects so those projects have time to implement any new features from Oslo. Per the policy[1] we freeze one week before the non-client library feature freeze, which is coming in two weeks. Therefore, we have

[openstack-dev] [cinder][security][api-wg] Adding http security headers

Hi, I have registered a blueprint for adding http security headers - https://blueprints.launchpad.net/cinder/+spec/http-security-headers Reason for introducing this change - I work for AT cloud project - Network Cloud (Earlier known as AT integrated Cloud). As part of working there we have

[openstack-dev] [manila] No meeting today July 5

We have a fair number of team members taking a holiday today and no new agenda items were added this week so let's skip today's community meeting. Next manila community meeting will be July 12 at 1500 UTC. https://wiki.openstack.org/wiki/Manila/Meetings Let's keep up with the reviews on

Re: [openstack-dev] [tc] Technical Committee Update for 3 July

Excerpts from Hongbin Lu's message of 2018-07-03 22:06:41 -0400: > > > > Discussions about affiliation diversity continue in two directions. > > Zane's proposal for requirements for new project teams has stalled a > > bit. The work Thierry and Mohammed have done on the diversity tags has > >

Re: [openstack-dev] [release-announce][ironic] ironic 11.0.0 (rocky)

I want to compliment the Ironic team on writing such engaging and comprehensive release notes. Nice work! Doug Excerpts from no-reply's message of 2018-07-05 10:24:19 +: > We are gleeful to announce the release of: > > ironic 11.0.0: OpenStack Bare Metal Provisioning > > This release is

Re: [openstack-dev] [all] log-classify project update (anomaly detection in CI/CD logs)

On July 3, 2018 7:39 am, Tristan Cacqueray wrote: [...] There is a lot to do and it will be challening. To that effect, I would like to propose an initial meeting with all interested parties. Please register your irc name and timezone in this etherpad:

Re: [openstack-dev] [publiccloud-wg] Meeting this afternoon for Public Cloud WG

Sorry guys, I'm not available once again. See you next time. Jean-Daniel Bonnetot ovh.com | @pilgrimstack On 05/07/2018 09:59, "Tobias Rydberg" wrote: Hi folks, Time for a new meeting for the Public Cloud WG. Agenda draft can be found at

[openstack-dev] [publiccloud-wg] Meeting this afternoon for Public Cloud WG

Hi folks, Time for a new meeting for the Public Cloud WG. Agenda draft can be found at https://etherpad.openstack.org/p/publiccloud-wg, feel free to add items to that list. See you all at IRC 1400 UTC in #openstack-publiccloud Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter &

Re: [openstack-dev] [tc] Technical Committee Update for 3 July

Jeremy Stanley wrote: On 2018-07-04 16:38:41 -0500 (-0500), Sean McGinnis wrote: [...] I would propose based on this lack of feedback that we go back to just having our predesignated office hour times, and anyone interested in catching up on what, if anything, was discussed during office hours