Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Juno Whatever gets it done faster- let me get the three repos aligned. I need to get the ovs/ovn work done so networking-ovn can call it, and the networking-sfc can call networking-ovn. Hopefully I will have it done tomorrow or over the weekend - let's touch base Monday or Sunday night.

Re: [Openstack] [Swift] 404 re-reading just created container

On 03/06/16 16:09, Mark Kirkwood wrote: I'll dig up the Haproxy config and post. However any thoughts in the meantime? We have: defaults log global maxconn 8000 option redispatch retries 3 stats enable timeout http-request 10s timeout queue 1m timeout connect 10s

[openstack-dev] What's Up, Doc? 3 June 2016

Hi everyone, I'm very pleased to be able to announce the results of our Install Guide naming poll this week. We ended up with 31 responses, and a very clear winner in "OpenStack Installation Tutorial". Thank you to everyone who voted! Also, just a note that I'm still very much in need of

[Openstack] [Swift] 404 re-reading just created container

Hi, I did previously mention that I would start a new thread if I could reproduce 'unexplained 404s'. Well, I can - however not for the exact case I mentioned in the previous thread. I have some python code using python-swiftclient that does: for a number of containers: create the

[OpenStack-Infra] [openstack-dev] [Infra][tricircle] patch not able to be merged

Hello, There is one quite strange issue in Tricircle stable/mitaka branch (https://github.com/openstack/tricircle/tree/stable/mitaka) . Even the patch ( https://review.openstack.org/#/c/324209/ ) were given Code-Review +2 and Workflow +1, the gating job not started, and the patch was not

[openstack-dev] [Infra][tricircle] patch not able to be merged

Hello, There is one quite strange issue in Tricircle stable/mitaka branch (https://github.com/openstack/tricircle/tree/stable/mitaka) . Even the patch ( https://review.openstack.org/#/c/324209/ ) were given Code-Review +2 and Workflow +1, the gating job not started, and the patch was not

Re: [Openstack] Heat create-stack fails.

Hi Eugen, For some reason, I'm not getting any email from this list. My mailserver doesn't even show any attempts from the list server. Anyway, the install guide does not specify what the auth_plugin is suppose to be. By default auth_plugin is depreciated. # Authentication type to load

Re: [openstack-dev] [horizon] new stable-maint cores for Horizon

On Thu, Jun 02, 2016 at 08:27:29AM +0200, Matthias Runge wrote: > Horizoners, > > please join me to welcome > > * Richard Jones > * Rob Cresswell > * Thai Tran > > as new Horizon stable core reviewers. > > Thank you guys for stepping up and thank you tonyb for pulling stats and > pushing this.

[openstack-dev] openstack Unauthorized HTTP 401 'Could not find user' when sahara call heat

Hi, Friends, I used Openstack-Juno heat, keystone and Mitaka sahara in CentOS7. Sahara is installed in docker container using host network. When sahara wants to call heat to create a hadoop cluster, the below error is happened. Could you help to check this issue? I guess, the heat

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, I agree with submitting WIP patches to community, because you already did many works on networking-sfc and networking-ovn, it is better that you submit the initial patches about networking-sfc and networking-ovn, then me and Srilatha take over the patches. Do you have time to do it?

[openstack-dev] [kolla] Google Hangouts discussion for dueling specifications for Dockerfile customization

Hey folks, IRC and mailing list were going far too slow for us to make progress on the competing specifications for handling Dockerfile customization. Instead we held a hangout, which I don't like because it isn't recorded, but it is high bandwidth and permitted us to work through the problem

[openstack-dev] [nova][SR-IOV/PCI] SR-IOV/PCI CI for mutli node

Hi, As part of the Performance VMs CI and technical debt session we had in Ausin summit, we decide to focus on fixing pci resize and migration bugs. Currently the pci resize patch [1] and migration patch [2] are up for review. The resize patch is tested with Intel PCI CI

[openstack-dev] [tc][security] Item #5 of the VMT

Hi folks, I think we are nearly done with Item #5 [1] of the VMT. One question remains. We need to know which repo the analysis documentation will land in . There is security-doc we could use for this purpose, but we could also create a new repository called "security-analysis" (or open to

Re: [Openstack-operators] problem with DVR in Kilo and floating IPs

Hi, We have seen this kind of behaviour and it was because the qrouter had the following rules : -A neutron-postrouting-bottom -m comment --comment "Perform source NAT on outgoing traffic." -j neutron-l3-agent-snat -A neutron-l3-agent-snat -j neutron-l3-agent-float-snat -A

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

On 06/02/2016 07:22 PM, Henry Nash wrote: Hi As you know, I have been working on specs that change the way we handle the uniqueness of project names in Newton. The goal of this is to better support project hierarchies, which as they stand today are restrictive in that all project names

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

As an operator that has clouds that are partitioned into different host aggregates with different flavors targeting them, I totally believe we will have users that want to have a single k8s cluster span multiple different flavor types. I'm sure once I deploy magnum, I will want it too. You

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hongbin, Have you considered a workflow engine? FWIW I agree with Adrian about the difficulties of heterogenous systems. Much better to operate, and in reality the world has moved entirely to x86_64 + Linux. I could see a future in which ARM breaks into the server space, but that is multiple

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

On Thu, Jun 02, 2016 at 08:41:40AM -0700, John Dickinson wrote: > open swift/swiftclient patches to stable/kilo have been abandoned Thanks John Tony. signature.asc Description: PGP signature __ OpenStack Development

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

On Thu, Jun 02, 2016 at 07:10:23PM -0400, Emilien Macchi wrote: > I think that all openstack/puppet-* projects that have stable/kilo can > be kilo-EOLed. > Let me know if it's ok and I'll abandon all open reviews. Totally fine with me. I've added them. Feel free to abanond the reviews. Any

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

On Thu, Jun 02, 2016 at 12:38:15PM +0200, Ihar Hrachyshka wrote: > I think all networking-* repos should EOL too, since they are plugins to > neutron which is already EOL. I struggle to find a way that could maintain > their gate without neutron. Thanks I've added them. Yours Tony.

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

I am really struggling to accept the idea of heterogeneous clusters. My experience causes me to question whether a heterogeneus cluster makes sense for Magnum. I will try to explain why I have this hesitation: 1) If you have a heterogeneous cluster, it suggests that you are using external

[openstack-dev] [keystone] Changing the project name uniqueness constraint

Hi As you know, I have been working on specs that change the way we handle the uniqueness of project names in Newton. The goal of this is to better support project hierarchies, which as they stand today are restrictive in that all project names within a domain must be unique, irrespective of

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

On Thu, Jun 2, 2016 at 6:31 AM, Tony Breeds wrote: > Hi all, > In early May we tagged/EOL'd several (13) projects. We'd like to do a > final round for a more complete set. We looked for projects meet one or more > of the following criteria: > - The project is

[Openstack-operators] oslo_messaging, rabbit, ssl and mitaka and xenial

Hi all, We’ve been trying out some mitaka packages as well as some Xenial hosts and have been having some issues with rabbit and SSL. If using rabbitMQ 3.6.x on Trusty I can’t get a mitaka host (oslo_messaging 4.6.1, python-amqp 1.4.9) to connect to rabbit over SSL. If I use rabbitMQ 3.6.x

Re: [Openstack-operators] Uptime and SLA's

Hey Matt, I am looking into Monasca and would like to know your recommendation for resources regarding a) understanding and b) installing the project; especially since there is no install guide on the project wiki. Additionally, can you shed some light on whether this setup would run behind a

[openstack-dev] [octavia] enabling new topologies

Stephen, Michael, thank you for having a look. I'll respond to every issue you mentioned when I get to work on Sunday. Until then, in case you don't mind inspecting a small diff, just to clarify my point, please have a look at a rather straightforward change, which 1. exemplifies pretty much

Re: [openstack-dev] [magnum][lbaas] Operator-facing installation guide

Brandon, Magnum uses neutron’s LBaaS service to allow for multi-master bays. We can balance connections between multiple kubernetes masters, for example. It’s not needed for single master bays, which are much more common. We have a blueprint that is in design stage for de-coupling magnum from

Re: [Openstack-operators] Uptime and SLA's

We do this a few different ways, some of which may meet your needs. For API calls we measure a simple, quick, and impactless call for each service (like heat stack-list) and we monitor East from West and vice versa. The goal here is nothing added to the DBs, so nothing like neutron net-create.

[Openstack] problem with DVR in Kilo and floating IPs

Hi, Using DVR in Kilo, I've the following issue: - VM1 is in tenant network 1 (fixed IP 10.97.2.4) - VM2 is in tenant network 2 (fixed IP 10.97.0.4) - a router connects both networks - VM1 and VM2 both have floating IPs - I can ping from VM1 to VM2 using fixed / internal IP - I cannot SSH from

Re: [openstack-dev] [Kolla] About kolla-ansible reconfigure

Hu, Reconfigure was not designed to handle changes to globals.yml. I think its a good goal that it should be able to do so, but it does not today. Reconfigure was designed to handle changes to /etc/kolla/config/* (where custom config for services live). Reconfigure in its current incarnation

[Openstack-operators] problem with DVR in Kilo and floating IPs

Hi, Using DVR in Kilo, I've the following issue: - VM1 is in tenant network 1 (fixed IP 10.97.2.4) - VM2 is in tenant network 2 (fixed IP 10.97.0.4) - a router connects both networks - VM1 and VM2 both have floating IPs - I can ping from VM1 to VM2 using fixed / internal IP - I cannot SSH from

Re: [openstack-dev] [Ironic] Changes to Ramdisk and iPXE defaults in Devstack and many gate jobs

These changes have all merged and taken effect. Ironic and IPA gate jobs are now operating as mentioned below, with one change; during review it was decided to lower the amount of ram per node to 384mb instead of 512mb of RAM. This will ensure that we don't add additional bloat to TinyIPA

[openstack-dev] [Ironic] Completed: Move to TinyIPA Ramdisk and iPXE defaults in gate jobs

These changes have all merged and taken effect. Ironic and IPA gate jobs are now operating as mentioned below, with one change; during review it was decided to lower the amount of ram per node to 384mb instead of 512mb of RAM. This will ensure that we don't add additional bloat to TinyIPA

Re: [openstack-dev] [magnum][lbaas] Operator-facing installation guide

Call me ignorance, but I'm surprised at neutron-lbaas being a dependency of magnum. Why is this? Sorry if it has been asked before and I've just missed that answer? Thanks, Brandon On Wed, 2016-06-01 at 14:39 +, Hongbin Lu wrote: > Hi lbaas team, > > > > I wonder if there is an

[openstack-announce] [new][manila] python-manilaclient 1.9.0 release (newton)

We are excited to announce the release of: python-manilaclient 1.9.0: Client library for OpenStack Manila API. This release is part of the newton release series. With source available at: https://git.openstack.org/cgit/openstack/python-manilaclient With package available at:

[openstack-dev] [Manila] v1 API and nova-net support removal in newton

We have made the decision to remove the v1 API from Manila in Newton (it was deprecated in Mitaka). Only v2.0+ will be supported. For those that don't know, v2.0 is exactly the same as v1 but it has microversion support. You need a client library from Liberty or Mitaka to get microversion

[openstack-dev] [Manila] Newton deadlines (reminder)

At the start of the Newton release we agreed to keep the same deadlines we had for Mitaka. I thought everyone knew what those were but there is some confusion so I'll remind everyone. As always, we will enforce a Feature Freeze on the N-3 milestone date: September 1st [1]. Only bugfixes and

Re: [openstack-dev] [ironic] versioning of IPA, it is time or is it?

2 июня 2016 г. 10:19 PM пользователь "Loo, Ruby" написал: > > Hi, > > I recently reviewed a patch [1] that is trying to address an issue with ironic (master) talking to a ramdisk that has a mitaka IPA lurking around. > > It made me think that IPA may no longer be a teenager

Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News

Hello, I think we need to increase the cap for real operators and not vendors but I have not attended the Ops meetups WG meetings so I do not know all the context about it. BTW. DO we have a place and date for the next mid-cycle one? Edgar On 6/2/16, 1:16 PM, "Melvin Hillsman"

[openstack-dev] [Manila] Midcycle meetup

As of now we're planning to hold our midcycle meetup in virtually on June 28, 29, and possibly June 30 (depending on agenda). If any core reviewers or significant contributors can't attend those days please let me know. Also if anyone wants to travel to RTP to join those of us based here I

Re: [openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 6/2/2016

Thanks Artur for this summarize. > On Jun 2, 2016, at 3:29 PM, Korzeniewski, Artur > wrote: > > Hi Neutrinos, > I would like to start the first bi-weekly upgrades work report. > > TLDR: > In order to inform community what is going on in upgrades field, we would

[Openstack-operators] Uptime and SLA's

We¹re currently in the process of writing up an internal SLA for our openstack cloud, I¹d be interested to hear what others have done and what metrics folks are capturing. My initial thoughts are success / fail spawning instances, creating and attaching volumes, API availability and so on. Can

[openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 6/2/2016

Hi Neutrinos, I would like to start the first bi-weekly upgrades work report. TLDR: In order to inform community what is going on in upgrades field, we would like to start bi-weekly reporting. We would like to show progress in database resource transition to Oslo VersionedObjects. Also list

Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News

Apologies, * On a side note, can we decide on a [email-subject-tag] to help filter these in [Openstack-operators] * Suggestion: [ops-meetups-team] For the delay that is since rain and Houston, TX fight a lot and rain is winning these days unfortunately. I was tasked with submitting to the ML a

[openstack-announce] [new][openstackansible] openstack-ansible-rsyslog_server 13.1.2 release

We are pumped to announce the release of: openstack-ansible-rsyslog_server 13.1.2: rsyslog_server for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-rsyslog_server 13.1.0..13.1.2 -- 2a9efa8 Role tests

[openstack-announce] [new][openstackansible] openstack-ansible-rabbitmq_server 13.1.2 release

We are tickled pink to announce the release of: openstack-ansible-rabbitmq_server 13.1.2: rabbitmq_server for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-rabbitmq_server 13.1.0..13.1.2 --- b989aad

[openstack-announce] [new][openstackansible] openstack-ansible 12.0.14 release

We are psyched to announce the release of: openstack-ansible 12.0.14: Ansible playbooks for deploying OpenStack With source available at: http://git.openstack.org/cgit/openstack/openstack-ansible For more details, please see below. 12.0.14 ^^^ New Features * The

[openstack-announce] [new][openstackansible] openstack-ansible-os_nova 13.1.2 release

We are jazzed to announce the release of: openstack-ansible-os_nova 13.1.2: os_nova for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-os_nova 13.1.0..13.1.2 --- bc56eac Add dependencies for paramiko 2.0

[openstack-announce] [new][horizon] horizon 9.0.1 release (mitaka)

We are pumped to announce the release of: horizon 9.0.1: OpenStack Dashboard This release is part of the mitaka stable release series. For more details, please see below. Changes in horizon 9.0.0..9.0.1 --- 99dc305 Imported Translations from Zanata 838b824 UX:

[openstack-announce] [new][openstackansible] openstack-ansible-os_horizon 13.1.2 release

We are pleased to announce the release of: openstack-ansible-os_horizon 13.1.2: OpenStack Horizon role for OpenStack Ansible For more details, please see below. 13.1.2 ^^ New Features * The new LBaaS v2 dashboard is available in Horizon. Deployers can enable the panel by setting the

[openstack-announce] [new][openstackansible] openstack-ansible-ironic 13.1.2 release

We are delighted to announce the release of: openstack-ansible-ironic 13.1.2: Ironic Role for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-ironic 13.1.0..13.1.2 -- 9f17867 Role tests should test against the

[openstack-announce] [new][openstackansible] openstack-ansible-os_heat 13.1.2 release

We are chuffed to announce the release of: openstack-ansible-os_heat 13.1.2: os_heat for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-os_heat 13.1.0..13.1.2 --- c1d1216 Role tests should test against the same

[openstack-announce] [new][openstackansible] openstack-ansible-os_neutron 13.1.2 release

We are overjoyed to announce the release of: openstack-ansible-os_neutron 13.1.2: os_neutron role for OpenStack- Ansible For more details, please see below. 13.1.2 ^^ Upgrade Notes * As described in the Mitaka release notes (http://docs.openstack.org/releasenotes/neutron/mitaka.html)

[openstack-announce] [new][openstackansible] openstack-ansible-os_cinder 13.1.2 release

We are pumped to announce the release of: openstack-ansible-os_cinder 13.1.2: os_cinder role for OpenStack- Ansible For more details, please see below. Changes in openstack-ansible-os_cinder 13.1.1..13.1.2 - 12a1e1c Added task to install apt

[openstack-announce] [new][openstackansible] openstack-ansible-os_glance 13.1.2 release

We are jubilant to announce the release of: openstack-ansible-os_glance 13.1.2: os_glance for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-os_glance 13.1.0..13.1.2 - 835aef8 Add dependencies for paramiko

[openstack-announce] [new][openstackansible] openstack-ansible-plugins 13.1.2 release

We are eager to announce the release of: openstack-ansible-plugins 13.1.2: plugins for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-plugins 13.1.1..13.1.2 --- d1f38d5 Adjust release note for config template

[openstack-announce] [new][openstackansible] openstack-ansible-os_keystone 13.1.2 release

We are amped to announce the release of: openstack-ansible-os_keystone 13.1.2: os_keystone for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-os_keystone 13.1.0..13.1.2 --- 4bbf773 Add dependencies for

[openstack-announce] [new][openstackansible] openstack-ansible-os_aodh 13.1.2 release

We are chuffed to announce the release of: openstack-ansible-os_aodh 13.1.2: os_aodh for OpenStack Ansible For more details, please see below. Changes in openstack-ansible-os_aodh 13.1.0..13.1.2 --- 1621cce Add dependencies for paramiko 2.0

[openstack-announce] [new][openstackansible] openstack-ansible 13.1.2 release

We are gleeful to announce the release of: openstack-ansible 13.1.2: Ansible playbooks for deploying OpenStack With source available at: http://git.openstack.org/cgit/openstack/openstack-ansible For more details, please see below. 13.1.2 ^^ New Features * The new LBaaS

[openstack-dev] [ironic] versioning of IPA, it is time or is it?

Hi, I recently reviewed a patch [1] that is trying to address an issue with ironic (master) talking to a ramdisk that has a mitaka IPA lurking around. It made me think that IPA may no longer be a teenager (yay, boo). IPA now has a stable branch. I think it is time it grows up and acts

[openstack-announce] [new][openstackansible] openstack-ansible-os_ceilometer 13.1.2 release

We are excited to announce the release of: openstack-ansible-os_ceilometer 13.1.2: os_ceilometer role for OpenStack-Ansible For more details, please see below. Changes in openstack-ansible-os_ceilometer 13.1.0..13.1.2 - abec6e0 Role tests

[openstack-announce] [new][openstackansible] openstack-ansible-security 13.1.2 release

We are jazzed to announce the release of: openstack-ansible-security 13.1.2: Security hardening role for openstack-ansible For more details, please see below. 13.1.2 ^^ Bug Fixes * The dictionary-based variables in "defaults/main.yml" are now individual variables. The dictionary-based

[openstack-announce] [new][openstackansible] openstack-ansible-memcached_server 13.1.2 release

We are delighted to announce the release of: openstack-ansible-memcached_server 13.1.2: memcached_server for OpenStack Ansible For more details, please see below. 13.1.2 ^^ New Features * The openstack-ansible-memcached_server role includes a new override,`memcached_connections` which

Re: [openstack-dev] [octavia] enabling new topologies

Hi Sergey, Welcome to working on Octavia! I'm not sure I fully understand your proposals, but I can give my thoughts/opinion on the challenge for Active/Active. In general I agree with Stephen. The intention of using TaskFlow is to facilitate code reuse across similar but different code flows.

Re: [openstack-dev] [octavia] is l7 rule using routed L3 connectivity

I agree that if this occurred it is a bug. Please open a bug for us in launchpad and include your controller worker logs and amphora-agent log from the impacted amphora. Thanks, Michael On Wed, Jun 1, 2016 at 9:55 AM, Stephen Balukoff wrote: > Hello Yong Sheng Gong! > >

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Has an email been posted to the [heat] community for their input? Maybe I missed it. Thanks, -Keith On 6/2/16, 9:42 AM, "Hongbin Lu" wrote: >Madhuri, > >It looks both of us agree the idea of having heterogeneous set of nodes. >For the implementation, I am open to

Re: [openstack-dev] [freezer] Addition to the core team

+1 Sent from my Samsung device Original message From: "Ramirez Garcia, Guillermo" Date: 02/06/2016 17:40 (GMT+01:00) To: "Mathieu, Pierre-Arthur" , openstack-dev@lists.openstack.org Cc:

Re: [openstack-dev] [qa] [Tempest] Abondoned old code reviews

Thanks for feedback here. There are not any objections, so I will drop old code reviews on Tempest queue. Thanks Ken Ohmichi --- 2016-05-31 23:55 GMT-07:00 Masayuki Igawa : > On Wed, Jun 1, 2016 at 3:05 AM, Andrea Frittoli > wrote: >> On

[openstack-announce] [OSSA-2016-008] Incorrect Audit IDs in Keystone Fernet Tokens can result in revocation bypass (CVE-2016-4911)

OSSA-2016-008: Incorrect Audit IDs in Keystone Fernet Tokens can result in revocation bypass :Date: May 23,

Re: [Openstack] cinder_img_volume_type value for a NFS shared storage ...

Hi Jean-Pierre, Related to my use case , what should be the value of the cinder_img_volume_type property I’ve to add to the image :/ nfstype or nfsbackend ?/ You need to choose a glance image which has "nfstype" volume_type in the property cinder_img_volume_type. If you don't have a image

Re: [openstack-dev] [congress] Spec for congress.conf

Bryan, I spent some time looking into the proper way to document configuration options in OpenStack. There's a configuration reference that's part of the openstack-manuals project. It'll take some time to figure out the best way of contributing to that. But for now I added a section to our

Re: [openstack-dev] [nova] API changes on limit / marker / sort in Newton

On 06/02/2016 12:53 PM, Everett Toews wrote: > >> On Jun 1, 2016, at 2:01 PM, Matt Riedemann >> wrote: >> >> Agree with Sean, I'd prefer separate microversions since it makes getting >> these in easier since they are easier to review (and remember we make >>

Re: [openstack-dev] [nova] [scheduler] New filter: AggregateInstanceAffinityFilter

> -Original Message- > From: Alonso Hernandez, Rodolfo > [mailto:rodolfo.alonso.hernan...@intel.com] > Sent: Thursday, June 2, 2016 6:00 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [nova]

Re: [Openstack] Windows 10 guest benchmark

Reza, I found this article about bluescreen of Windows 10 Professional running on KVM. Not sure if this is useful to you.

Re: [openstack-dev] [keystone][security] Service User Permissions

> On Jun 2, 2016, at 10:58 AM, Adam Young wrote: > > Any senseible RBAC setup would support this, but we are not using a sensible > one, we are using a hand rolled one. Replacing everything with Fortress > implies a complete rewrite of what we do now. Nuke it from orbit

[Openstack] Windows 10 guest benchmark

Hi, I'm trying to benchmark Windows 10 guest OS on different hypervisors including OpenStack with KVM. Unfortunately, guest OS on OpenStack (KVM) shows blue screen and needs to be restarted immediately after starting any stress benchmark (likes Sandra). I've built Windows 10 guest OS with VirtIO

[openstack-dev] [nova] [scheduler] New filter: AggregateInstanceAffinityFilter

Hello: For the last two cycles we have tried to introduce a new filter to be able to interact better with the aggregates, using the metadata to accept or reject an instance depending on the flavor: https://review.openstack.org/#/c/189279/ This filter was reverted and we agreed to

[Openstack] Openstack Mitaka - Neutron configuration

Hi! I have a small question regarding the Neutron configuration in Mitaka. I have been following the Ubuntu 14.04 guide with the provider and self-service model. Everything works fine and I can get an public ip address or a private one depending on where I spawn the instance. That said, is

Re: [openstack-dev] [nova] API changes on limit / marker / sort in Newton

> On Jun 1, 2016, at 2:01 PM, Matt Riedemann wrote: > > Agree with Sean, I'd prefer separate microversions since it makes getting > these in easier since they are easier to review (and remember we make changes > to python-novaclient for each of these also). > >

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 06/02/2016 11:03:28 AM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , "disc...@openvswitch.org" > , Justin Pettit , >

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

Greetings OpenStack community, This week there are no new merged guidelines nor guidelines proposed for freeze but there is a new guideline discussing ways to ensure that URIs are semantically consistent: https://review.openstack.org/#/c/322194/ # Recently merged guidelines These guidelines

[Openstack-operators] [recognition] AUC Recognition WG Meeting Today (6/2/16)

Hi everyone, The AUC (Active User Contributor) Recognition WG will be meeting today and the agenda has been posted on our wiki[1]. Meeting information: Date: 6/2 Time: 1900 UTC IRC Channel: #openstack-meeting-3 [1] *https://wiki.openstack.org/wiki/AUCRecognition#Meeting_Information

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Juno, Sure make sense. I will have ovs/ovn in rough shape by end of week (hopefully) that will allow you to call the interfaces from networking-ovn. Ryan has asked that we submit WIP patches etc so hopefully that will kickstart the review process. Also, hopefully some of the networking-sfc

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, Sure - may need some help and it will probably be next week before I get to it. Regards John From: Ryan Moats > Date: Wednesday, June 1, 2016 at 1:25 PM To: John McDowall >

Re: [openstack-dev] [keystone][security] Service User Permissions

On 06/02/2016 11:36 AM, Shawn McKinney wrote: On Jun 2, 2016, at 10:03 AM, Adam Young wrote: To do all of this right, however, requires a degree of introspection that we do not have in OpenStack. Trove needs to ask Nova "I want to do X, what role do I need?" and there is

Re: [openstack-dev] [Monasca][Gnocchi] influxDB clustering and HA will be "commercial option".

Has anyone talked with the gnocchi folks? It seems like a good time to. :) Thanks, Kevin From: Jay Pipes [jaypi...@gmail.com] Sent: Thursday, June 02, 2016 4:55 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Monasca] influxDB

Re: [openstack-dev] [freezer] Addition to the core team

+1 -Original Message- From: Mathieu, Pierre-Arthur Sent: Thursday 2 June 2016 16:29 To: openstack-dev@lists.openstack.org Cc: freezer-eskimos Subject: [openstack-dev][freezer] Addition to the core team Hello, I would like to propose that we make

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

open swift/swiftclient patches to stable/kilo have been abandoned --John On 2 Jun 2016, at 4:45, Jesse Pretorius wrote: > Hi Tony, > > OpenStack-Ansible is just waiting for the requirements repository and the > swift repository kilo-eol tags. Once they're done we'd like to bump the > SHA's

[openstack-dev] [networking-sfc] how to install networking-sfc on compute node

Hi, >From this link https://github.com/openstack/networking-sfc/tree/master/devstack, it is about installing networking-sfc together with neutron-server, I want to install networking-sfc on compute node, can anyone tell me how to set the local.conf? Regards, Juno Zhu IBM China Development

Re: [openstack-dev] Collecting our wiki use cases

On 06/02/2016 10:59 AM, Thierry Carrez wrote: > Thanks to everyone who helped collecting wiki use cases on that etherpad. > > I tried to categorize the various use cases and I think they fit in 4 > categories: > > 1/ Things that are already in the process of being moved to reference > websites

Re: [openstack-dev] [freezer] Addition to the core team

Small correction for the final line of the last email. I am proposing Deklan and not Saad as core. - Pierre From: Mathieu, Pierre-Arthur Sent: Thursday, June 2, 2016 4:29:29 PM To: openstack-dev@lists.openstack.org Cc: freezer-eskimos Subject:

Re: [openstack-dev] [keystone][security] Service User Permissions

> On Jun 2, 2016, at 10:03 AM, Adam Young wrote: > > To do all of this right, however, requires a degree of introspection that we > do not have in OpenStack. Trove needs to ask Nova "I want to do X, what role > do I need?" and there is no where in the system today that

Re: [openstack-dev] [Nova] State machines in Nova

On 01/06/16 13:50, Andrew Laski wrote: This is a great point. I think most people have an implicit assumption that the state machine will be exposed to end users via the API. I would like to avoid that for exactly the reason you've mentioned. Of course we'll want to expose something to users but

[openstack-dev] [freezer] Addition to the core team

Hello, I would like to propose that we make Deklan Dieterly (ddieterly) core on freezer. He has been a highly valuable developper for the past few month, mainly working on integration testing for Freezer components. He has also been helping a lot with features and Ux testing. His work can be

Re: [openstack-dev] [neutron][dvr] Wasting so many external network IPs in DVR mode?

On Thu, Jun 2, 2016 at 12:04 AM, zhi wrote: > The reason putting the routers namespaces behind the fip namespace is > saving mac address tables in switches. In Centralized Virtual Router, there > are many "qg" interfaces in the external bridge. Every "qg" interface

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hongbin, for the implementation of heterogeneous, I think we should avoid to talking with nova or other service directly, which will bring lots of coding. maybe the best way is to refactor our heat template, and let a bay support several heat template when we scale-out new node or delete

Re: [Openstack] Collecting our wiki use cases

Thanks to everyone who helped collecting wiki use cases on that etherpad. I tried to categorize the various use cases and I think they fit in 4 categories: 1/ Things that are already in the process of being moved to reference websites or documentation That would be the main "portal" page

Re: [Openstack-operators] Collecting our wiki use cases

Thanks to everyone who helped collecting wiki use cases on that etherpad. I tried to categorize the various use cases and I think they fit in 4 categories: 1/ Things that are already in the process of being moved to reference websites or documentation That would be the main "portal" page

Re: [openstack-dev] [keystone][security] Service User Permissions

On 06/02/2016 01:23 AM, Jamie Lennox wrote: Hi All, I'd like to bring to the attention of the wider security groups and OpenStack users the Service Users Permissions [1] spec currently proposed against keystonemiddleware. To summarize quickly OpenStack has long had the problem of token

Re: [openstack-dev] Collecting our wiki use cases

Thanks to everyone who helped collecting wiki use cases on that etherpad. I tried to categorize the various use cases and I think they fit in 4 categories: 1/ Things that are already in the process of being moved to reference websites or documentation That would be the main "portal" page

  1   2   >