[Openstack] [nova] Nova-scheduler: when are filters applied?

Sorry. I was to quick with the send button... Hi *, I posted my question in [1] a week ago, but no answer yet. When does Nova apply its filters (Ram, CPU, etc.)? Of course at instance creation and (live-)migration of existing instances. But what about existing instances that have been shutdown

Re: [Openstack] [nova]

On 08/30/2018 10:19 AM, Eugen Block wrote: When does Nova apply its filters (Ram, CPU, etc.)? Of course at instance creation and (live-)migration of existing instances. But what about existing instances that have been shutdown and in the meantime more instances on the same hypervisor have been

[Openstack] [nova]

Hi *, I posted my question in [1] a week ago, but no answer yet. When does Nova apply its filters (Ram, CPU, etc.)? Of course at instance creation and (live-)migration of existing instances. But what about existing instances that have been shutdown and in the meantime more instances on the

[openstack-dev] [tripleo] quickstart for humans

Hello! Over the last few months, it seems that tripleo-quickstart has evolved into a CI tool. It's primarily used by computers, and not humans. tripleo-quickstart is a helpful set of ansible playbooks, and a collection of feature sets. However, it's become less useful for setting up development

[openstack-dev] [L2-Gateway]

Hello, I am trying to get the l2gw feature installed on an openstack install on centos 7 using the rdo queens repo. Initially I installed the l2gw rpms form the repo: yum install openstack-neutron-l2gw-agent

[openstack-dev] [Freezer] Set up the Freezer team meeting

Hi Geng, Could you please help us to set up the team meeting as you're the new PTL? It supposes to be now on #openstack-meeting-alt. I sent you messages about this but haven't got anything back from you. Thanks, *Trinh Nguyen *| Founder & Chief Architect *E:*

Re: [openstack-dev] [neutron] tox-siblings alternative for local testing

On 8/30/18 5:49 AM, Michel Peterson wrote: > > There are pre releases available in PyPI [1]. You can use those from > your requirements like we did in n-odl [2]. > > That might be an acceptable solution. > > [1] https://pypi.org/project/neutron/#history > [2]

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

This topic has surfaced intermittently ever since keystone implemented fernet tokens in Kilo. An initial idea was written down shortly afterwords [0], then we targeted it to Ocata [1], and removed from the backlog around the Pike timeframe [2]. The commit message of [2] includes meeting links. The

Re: [OpenStack-Infra] starting zuul migration for cyborg team repositories

It is ready for remove Zuul configuration in project-config: https://review.openstack.org/#/c/592849/ On Fri, Aug 17, 2018 at 2:59 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the cyborg repositories > has begun. Please do not approve any changes to >

Re: [OpenStack-Infra] [goal][python3][rally] starting zuul migration for rally

It is ready for removing configuration on project-config: https://review.openstack.org/#/c/597517/ On Wed, Aug 29, 2018 at 11:05 PM Nguyễn Trí Hải wrote: > The migration of Zuul project settings for the > rally repositories has begun. > Please do not approve any changes to >

[openstack-dev] [Manila] no meeting today

I've had to travel unexpectedly, won't be able to chair the meeting today, and no one posted any agenda topics this week. The rocky release is imminent so we'll open up stable/rocky for backports soon. Stein specs repo is open. Please put PTG planning ideas in the etherpad [1]. PTG is less

Re: [openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

On 08/30/2018 04:55 AM, Balázs Gibizer wrote: Hi, Based on the Nova PTG planning etherpad [1] there is a need to talk about the current state of the bandwidth work [2][3]. Bence (rubasov) has already planned to show a small demo to Neutron folks about the current state of the implementation.

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300: > On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston > wrote: > > > Progress is also being tracked in a wiki page [4]. > > > > [4] https://wiki.openstack.org/wiki/Python3 > > > > That wiki page should only track teams or

Re: [openstack-dev] [neutron] tox-siblings alternative for local testing

On Wed, Aug 29, 2018 at 9:06 AM, Takashi Yamamoto wrote: > is there any preferred solution for this? > i guess the simplest solution is to make an intermediate release of neutron > and publish it on pypi. i wonder if it's acceptable or not. > There are pre releases available in PyPI [1]. You

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston wrote: > Progress is also being tracked in a wiki page [4]. > > [4] https://wiki.openstack.org/wiki/Python3 > That wiki page should only track teams or subteams should also be included there? I'm asking because it seems that some subteams appear

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

FWIW, instead of barbican, castellan could be used as a key manager. On 08/30/2018 12:23 PM, Adrian Turjak wrote: > > > On 30/08/18 6:29 AM, Lance Bragstad wrote: >> >> Is that what is being described here ?  >> >>

[openstack-dev] [heat][glance] Heat image resource support issue

Hi Glance team Glance V1 image API been deprecated for a long while, and V2 has been used widely. Heat image resource would like to change to use V2 as well, but there is an unsolved issue, which blocks us from adopting V2. Right now, to image create require Heat to download the image to Heat

Re: [openstack-dev] [goal][python3] week 3 update

On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann wrote: > | import zuul job settings from project-config | openstack/networking-odl > | https://review.openstack.org/597870 | master| > | switch documentation job to new PTI | openstack/networking-odl > |

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

On 30/08/18 6:29 AM, Lance Bragstad wrote: > > Is that what is being described here ?  > > https://docs.openstack.org/keystone/pike/admin/identity-credential-encryption.html > > > This is a separate mechanism for storing secrets, not necessarily > passwords (although I agree the term

[openstack-dev] [neutron] [neutron-fwaas] roadmap

Hi, The FWaaS V2 spec (https://specs.openstack.org/ openstack/neutron-specs/specs/mitaka/fwaas-api-2.0.html) describes quite some changes. Currently only some of that functionality seems to be implemented i.e. applying firewall groups on a L2/L3 port. Does a roadmap exist, describing

[openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

Hi, Based on the Nova PTG planning etherpad [1] there is a need to talk about the current state of the bandwidth work [2][3]. Bence (rubasov) has already planned to show a small demo to Neutron folks about the current state of the implementation. So Bence and I are wondering about bringing

Re: [openstack-dev] [Openstack-operators] [nova][cinder][neutron] Cross-cell cold migration

On 29/08, Matt Riedemann wrote: > On 8/29/2018 3:21 PM, Tim Bell wrote: > > Sounds like a good topic for PTG/Forum? > > Yeah it's already on the PTG agenda [1][2]. I started the thread because I > wanted to get the ball rolling as early as possible, and with people that > won't attend the PTG

Re: [openstack-dev] [nova][neutron] numa aware vswitch

On Thu, 2018-08-30 at 00:15 +, Guo, Ruijing wrote: > Hi, Stephen, Sean > > It worked as expected. Good to hear. What were you missing? If there are other gaps in the documentation, I'd be happy to fix them. Stephen > Thanks, > -Ruijing > > -Original Message- > From: Stephen

Re: [openstack-dev] [goal][python3] week 3 update

On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann wrote: > > OK, there are somewhere just over 100 patches for all of the neutron > > repositories, so I'm going to wait for a quieter time of day to submit > > them to avoid blocking other, smaller, bits of work. > > > > Doug > > Those patches are up

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Hey dims, Thanks your reply. Your suggestion is very important. > what would be the impact to projects? > what steps they would have to take? We can launch a project to publish OpenStack Projects APIs Schema for users and developers. But now OpenStack Projects have no APIs Schema definition.

<    1   2