Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> -Original Message- > From: GHANSHYAM MANN [mailto:ghanshyamm...@gmail.com] > Sent: Wednesday, June 15, 2016 9:59 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [tempest][nova][defcore] Add option

[openstack-dev] [Horizon] New procedure for releasing xstatic packages

Hi folks, It's been a lng time coming, but we're almost there. I've put up a BP outlining the steps we need to get over the line and start releasing those looong awaited updates of our xstatic packages: https://blueprints.launchpad.net/horizon/+spec/xstatic-release-process I'll be

Re: [openstack-dev] [Neutron] Stable/liberty breakage

Thanks for the updates. From: Aaron Rosen Reply-To: OpenStack List Date: Wednesday, June 15, 2016 at 10:19 PM To: OpenStack List Subject: Re: [openstack-dev] [Neutron] Stable/liberty breakage Sorry I

Re: [Openstack] Devstack Auth Error in Neutron

Hi Karun, You need to set authentication identity plugins , It defines on which user credential you want to execute open-stack commands . By default DevStack installs 2 mains users 1. admin 2. demo This is how you use the credentials of the user demo: stack@devstack:~/devstack$ source openrc

[Openstack-operators] Duplicates and confusion in nova policy.json files

Now that policy files in nova Liberty apparently work I’m going through the stock example one and see that there are duplicate entries in the policy.json like compute:create:forced_host os_compute_api:servers:create:forced_host Which one do I use to change who can do forced_host? both or a

Re: [openstack-dev] [tempest] the project specific config option not generated together with tempest.conf.sample

Hi, Matthew, Ok, Got it, will follow the Zaqar example. Thank you pointing out that not to reply in an existing thread. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Matthew Treinish [mailto:mtrein...@kortar.org] Sent: Thursday, June 16, 2016 3:40 AM To: OpenStack

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 16 June 2016 at 03:33, Matt Riedemann wrote: > On 6/13/2016 3:35 AM, Daniel P. Berrange wrote: > >> On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: >> >>> Hi, >>> >>> You may or may not be aware of the vlan-aware-vms effort [1] in >>> Neutron. If

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 16 June 2016 at 00:31, Carl Baldwin wrote: > I know I've been pretty quiet since I started this thread. Y'all have > been doing so well, I've just been reading the thread every day and > enjoying it. I thought I'd top post here to kind of summarize. > > I see wisdom in

Re: [OpenStack-Infra] Error with 'git review'

Andreas jaeger,  thank you. I have solved the problem.The contributor must be the Foundation Member not the Community Member.visit https://www.openstack.org/profile/  to change the membership. --From:Andreas Jaeger

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

This might come across a little trolly/devils advocate, but I mulled on it for a few days, and I think I need to send it, so... fingers crossed you can extract some value from my questions. On 15 June 2016 at 01:57, Thierry Carrez wrote: > Hi everyone, > > I just proposed

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Wed, Jun 15, 2016 at 6:12 AM, Matthew Treinish wrote: > On Tue, Jun 14, 2016 at 12:19:54PM -0700, Chris Hoge wrote: >> >> > On Jun 14, 2016, at 11:21 AM, Matthew Treinish >> > wrote: >> > >> > On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On 6/14/2016 8:57 AM, Thierry Carrez wrote: Hi everyone, I just proposed a new requirement for OpenStack "official" projects, which I think is worth discussing beyond the governance review: https://review.openstack.org/#/c/329448/ From an upstream perspective, I see us as being in the

[openstack-dev] [networking-bagpipe] how to deploy devstack with bgpvpn and bagpipe driver

Hi all, I would like to evaluate bgpvpn and bagpipe driver in my local machine. I cannot find any useful deployment guide about it. I find a github repository for it, but it seems out of date (3 months ago). I'd appreciate it if someone can provide a working devstack configuration for multiple

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 6/13/2016 3:35 AM, Daniel P. Berrange wrote: On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: Hi, You may or may not be aware of the vlan-aware-vms effort [1] in Neutron. If not, there is a spec and a fair number of patches in progress for this. Essentially, the goal is to

[openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

Tackers, It gives me great pleasure to propose Kanagaraj Manickam to join the Tacker core team. In a short time, Kanagaraj has grown into a key member of the Tacker team. His enthusiasm and dedication to get Tacker code base on par with other leading OpenStack projects is very much appreciated.

Re: [Openstack] Neutron networking in ten sentences?

>So where do the routers and "ports" come into this? So routers are just like normal routers in that they attach to multiple networks and route between them. Ports are the basic unit that represent access to a network. A VM can have an arbitrary number of ports attached to different networks and

Re: [openstack-dev] [Congress] Progress on Congress support in OPNFV Colorado

Very exciting development indeed! From: "SULLIVAN, BRYAN L" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, June 14, 2016 at 8:58 PM To: "OpenStack Development Mailing List (not for usage questions)"

Re: [Openstack] Neutron networking in ten sentences?

On Jun 16, 2016, at 1:10 AM, Kevin Benton wrote: > It's essentially the equivalent of Amazon VPC: https://aws.amazon.com/vpc/ Ah, perfect. That cleared up a lot, I've worked with VPCs before. Not much, but enough to get the picture. Thanx! So where do the routers and "ports" come into this? And

Re: [Openstack] Neutron networking in ten sentences?

It's essentially the equivalent of Amazon VPC: https://aws.amazon.com/vpc/ It allows tenants to create virtual networks and attach VMs to these networks without worrying about the details of how their traffic is actually carried across the operator's physical network. On Jun 15, 2016 16:59,

Re: [openstack-dev] [qa] Tempest pre-provisioned credentials in the gate

Big +1 for that which makes pre-provisioned cred testing more thoroughly. And at the end we should divide the existing jobs among dynamic and pre-provisioned account so that we would not leave any of them less tested. Thanks gmann From: Andrea Frittoli [mailto:andrea.fritt...@gmail.com] Sent:

[Openstack] Neutron networking in ten sentences?

Could someone please dumb it down for me in ten sentences or less? I'm well aware what a network and how to manage it. I've worked as a network administrator for several years, managing huge Cisco networks (thousands of routers, tens of thousands of physical and virtual hosts with VLANs, VPNs etc

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

QEMU has the ability to directly connect to iSCSI volumes. Running the iSCSI connections through the nova-compute host *seems* somewhat inefficient. There is a spec/blueprint and implementation that landed in Kilo:

[Openstack-operators] [app-catalog] App Catalog IRC meeting Thursday June 16th

Join us Thursday for our weekly meeting, scheduled for June 16th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog In addition to status

[openstack-dev] [app-catalog] App Catalog IRC meeting Thursday June 16th

Join us Thursday for our weekly meeting, scheduled for June 16th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog In addition to status

Re: [OpenStack-Infra] JJB's use of inspect plugin info requires administrator permissions

That's just a basic sample script. Here's a script that will give you more info: https://stackoverflow.com/questions/9815273/how-to-get-a-list-of-installed-jenkins-plugins-with-name-and-version-pair -Khai On Wed, Jun 15, 2016 at 4:32 PM, Thanh Ha wrote: > I

Re: [OpenStack-Infra] JJB's use of inspect plugin info requires administrator permissions

I took a look at the groovy script idea. I think it might work but would be a bit more involved than the example. It seems Jenkins.instance.pluginManager.plugins simply prints a list of all plugins without their details like version etc... Regards, Thanh On 14 June 2016 at 20:11, Zaro

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Wed, Jun 15, 2016 at 09:10:30AM -0400, Doug Hellmann wrote: > Excerpts from Chris Hoge's message of 2016-06-14 16:37:06 -0700: > > Top posting one note and direct comments inline, I’m proposing > > this as a member of the DefCore working group, but this > > proposal itself has not been accepted

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

Ryan, In-line Regards John From: Ryan Moats > Date: Tuesday, June 14, 2016 at 9:42 PM To: John McDowall > Cc: Na Zhu >, Srilatha

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

I know I've been pretty quiet since I started this thread. Y'all have been doing so well, I've just been reading the thread every day and enjoying it. I thought I'd top post here to kind of summarize. I see wisdom in the strategy suggested by Sean Mooney to make a very minimal change to os-vif

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

On 6/15/2016 3:10 PM, Paul Michali wrote: Is the plan to back port that change to Mitaka? Thanks, PCM On Wed, Jun 15, 2016 at 1:31 PM Matt Riedemann > wrote: On 6/14/2016 3:09 PM, Jay Pipes wrote: > > Yes. Code

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

>I wouldn't say linux bridges are totally outside of its domain because it relies on them for security groups. It relies on a side effect of their existence - iptables rules being applied to the veth interface. It does nothing to the actual linux bridge itself. If there was a way to plug a veth

Re: [openstack-dev] [nova][cinder] Integration testing for Nova API os-assisted-volume-snapshots

On Wed, Jun 15, 2016 at 07:01:17PM +0200, Jordan Pittier wrote: > On Wed, Jun 15, 2016 at 6:21 PM, Matt Riedemann > wrote: > ... > > Does someone have a link to a successful job run for one of those drivers? > > I'd like to see if they are testing volume snapshot and

[openstack-dev] [ironic] June 20 meeting cancelled

Hey all, The weekly ironic meeting for June 20 will be cancelled because it overlaps with our midcycle. Join the midcycle instead. :) We'll resume our normal schedule on June 27. // jim __ OpenStack Development Mailing

[openstack-dev] [ironic] Midcycle reminder

Hi all, Just a reminder that our midcycle is next week! Details are here: https://wiki.openstack.org/wiki/VirtualSprints#Ironic_Virtual_Newton_Midcycle https://wiki.openstack.org/wiki/Sprints#Future_sprints_for_Newton Etherpad: https://etherpad.openstack.org/p/ironic-newton-midcycle Please

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Wednesday, June 15, 2016 12:45 PM, Mooney, Sean K [sean.k.moo...@intel.com] wrote: > > On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) > > wrote: > > > >which generates an arbitrary name > > > > > > I'm not a fan of this approach because it requires coordinated > >

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

Is the plan to back port that change to Mitaka? Thanks, PCM On Wed, Jun 15, 2016 at 1:31 PM Matt Riedemann wrote: > On 6/14/2016 3:09 PM, Jay Pipes wrote: > > > > Yes. Code merged recently from Sahid does this: > > > > https://review.openstack.org/#/c/277422/ > >

Re: [openstack-dev] [Neutron] Stable/liberty breakage

> On 15 Jun 2016, at 22:06, Ihar Hrachyshka wrote: > > >> On 15 Jun 2016, at 21:19, Aaron Rosen wrote: >> >> Sorry I think I gave Gary some bad information here. >> >> After digging into this more, the actually underlying issue that we hit is >>

Re: [openstack-dev] [Neutron] Stable/liberty breakage

> On 15 Jun 2016, at 21:19, Aaron Rosen wrote: > > Sorry I think I gave Gary some bad information here. > > After digging into this more, the actually underlying issue that we hit is > that the packaged 'distro' version of stable/liberty that was running with > the

[openstack-dev] [tacker] Cancelling weekly meeting next week (Jun 21, 2016)

I'll be away next week attending OPNFV Summit. Hence cancelling Tacker irc meeting on Jun 21st. We will resume the week after - on Tuesday Jun 28th, https://wiki.openstack.org/wiki/Meetings/Tacker - Sridhar __ OpenStack

Re: [openstack-dev] [tempest] the project specific config option not generated together with tempest.conf.sample

Just a note, please don't start a new thread as a reply to an existing thread. (well unless you remove the In-Reply-To header from the message) There is more details on this here: https://wiki.openstack.org/wiki/MailingListEtiquette#Threading I almost missed this because it was part of a

Re: [openstack-dev] [Neutron] Stable/liberty breakage

Sorry I think I gave Gary some bad information here. After digging into this more, the actually underlying issue that we hit is that the packaged 'distro' version of stable/liberty that was running with the vmware-nsx repo included this patch set which is not in upstream stable/liberty

Re: [openstack-dev] [Neutron] Stable/liberty breakage

On Wed, Jun 15, 2016 at 2:59 PM, Ihar Hrachyshka wrote: > >> On 15 Jun 2016, at 20:18, Gary Kotton wrote: >> >> Hi, >> The following patch breaks stable liberty drivers - >> https://review.openstack.org/#/c/238745/ >> This means that plugins will need to

Re: [openstack-dev] [Neutron] Stable/liberty breakage

> On 15 Jun 2016, at 20:18, Gary Kotton wrote: > > Hi, > The following patch breaks stable liberty drivers - > https://review.openstack.org/#/c/238745/ > This means that plugins will need to be updated to support this. Would you mind sharing details about the breakage? It

Re: [OpenStack-Infra] Trouble deploying a job with a Groovy postbuild step via JJB

On Wed, Jun 15, 2016 at 5:43 PM, Wayne Warren wrote: > Have you watched the Jenkins master log file while attempting to upload the > JJB-generated configuration? Oftentimes there are helpful log messages or > stack traces that can point to the problem. As for me looking at the

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

> -Original Message- > From: Peters, Rawlin [mailto:rawlin.pet...@hpe.com] > Sent: Wednesday, June 15, 2016 7:02 PM > To: Kevin Benton > Cc: OpenStack Development Mailing List (not for usage questions) > > Subject: Re:

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Wed, Jun 15, 2016 at 2:01 PM, Peters, Rawlin wrote: > On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) wrote: >> >which generates an arbitrary name >> >> I'm not a fan of this approach because it requires coordinated assumptions. >> With the OVS hybrid

[openstack-dev] [Neutron] Stable/liberty breakage

Hi, The following patch breaks stable liberty drivers - https://review.openstack.org/#/c/238745/ This means that plugins will need to be updated to support this. What do we do: 1. Revert – which could break people using latest stable/liberty 2. Have a requirement that Neutron plugins be

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) wrote: > >which generates an arbitrary name > > I'm not a fan of this approach because it requires coordinated assumptions. > With the OVS hybrid plug strategy we have to make guesses on the agent side > about the presence of

Re: [Openstack-operators] NOVA build timeout: Time to fail a vm from build state

Ack. I'm picking my worst case with a 2T volume create and then doubling. On Wed, Jun 15, 2016 at 11:25 AM, Matt Riedemann wrote: > On 6/15/2016 12:09 PM, David Medberry wrote: > >> So, there is a nova.conf setting: >> >> instance_build_timeout (default to 0, never

Re: [openstack-dev] [nova] Virtuozzo (Compute) CI is incorrectly patching for resize support

On 6/15/2016 5:17 AM, Evgeny Antyshev wrote: Hello, Matt! First of all, I want to apologize for the inconvenience. This all started yesterday when I updated Virtuozzo CI using latest puppets, Zuul, Jenkins and other stuff. The update somehow led to Zuul not passing environment variables like

Re: [openstack-dev] [nova] Virtuozzo (Compute) CI is incorrectly patching for resize support

On 2016-06-15 13:17:54 +0300 (+0300), Evgeny Antyshev wrote: [...] > This all started yesterday when I updated Virtuozzo CI using latest puppets, > Zuul, Jenkins and other stuff. > The update somehow led to Zuul not passing environment variables like > ZUUL_CHANGE, LOG_PATH to Jenkins job. [...]

Re: [Openstack] nova "get-password " returns blank line

It all depends on how you have setup your cloud. Most/many OpenStack clouds DO NOT inject into the instance and the password feature is null and void. Look at: enable_instance_password = *True* (BoolOpt) Enables returning of the instance password by the relevant server API calls such as create,

Re: [Openstack-operators] Keystone to drop support for driver versioning…

Operators, We did not receive any feedback that dropping Keystone driver versioning would negatively impact anyone. Thus, the Keystone team met yesterday and decided to drop support for driver versioning. However, we will continue to support current legacy drivers. Moving forward though,

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

On 6/14/2016 3:09 PM, Jay Pipes wrote: Yes. Code merged recently from Sahid does this: https://review.openstack.org/#/c/277422/ Best, -jay That was actually reverted out of mitaka: https://review.openstack.org/#/c/292290/ The feature change that got into newton was this:

Re: [Openstack-operators] NOVA build timeout: Time to fail a vm from build state

On 6/15/2016 12:09 PM, David Medberry wrote: So, there is a nova.conf setting: instance_build_timeout (default to 0, never timeout) Does anyone have a "good" value they use for this? In my mind it falls very much into the specific-to-your-cloud-implementation bucket but just wondered what

Re: [Openstack] Restore nova instances after Ceph crash

Awesome. Thx for sharing! On Wed, Jun 15, 2016, 11:26 AM Eugen Block wrote: > Hi, > > this is no question for you guys, it's more of an information what I > was facing today and I wanted to share it if any of you should be > facing the same or similar issue. > > Due to an

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Excerpts from Kyle Mestery's message of 2016-06-15 09:05:59 -0500: > On Tue, Jun 14, 2016 at 9:15 AM, Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2016-06-14 15:57:10 +0200: > >> Hi everyone, > >> > >> I just proposed a new requirement for OpenStack

[Openstack-operators] NOVA build timeout: Time to fail a vm from build state

So, there is a nova.conf setting: instance_build_timeout (default to 0, never timeout) Does anyone have a "good" value they use for this? In my mind it falls very much into the specific-to-your-cloud-implementation bucket but just wondered what folks were usign for this setting (if any). 10

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

There have been a number of bug fixes to the NUMA code in both Mitaka and Newton. I think you would need to be very careful in your backporting :) -jay On 06/15/2016 09:55 AM, Paul Michali wrote: Yeah, was thinking more of technically vs policy. Wondering if there are other dependencies or if

[Openstack] nova "get-password " returns blank line

Hi, I'm trying to use nova get-password command. My centos-1 (using the "standard" CentOS OpenStack image) is running find and I'm able to log via ssh by using centos user and a key pair. But, the following command returns a blank line: [root@dhcp-10-128-11-58 tmp]# nova get-password

Re: [openstack-dev] [nova][cinder] Integration testing for Nova API os-assisted-volume-snapshots

On Wed, Jun 15, 2016 at 6:21 PM, Matt Riedemann wrote: > In the nova-api meeting today we were talking about the nova > os-assisted-volume-snapshots API and whether or not it was a proxy API to > cinder. We determined it's not, it performs an action on a server

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

> +1 to everything Daniel said. Nova really expects release-to-release > upgrades. We do online data migrations between releases. Maybe one > reason you're getting this to work is we have a nova-manage command to > force the migration of data between releases rather than doing the > online data

Re: [Openstack] How to set a host aggregate in several AZ via the GUI

On 06/15/2016 03:06 AM, Jean-Pierre Ribeauville wrote: Hi, Is it possible to add a same aggregate in several AZ via the Horizon GUI ? No this is not possible. An aggregate may only belong to a single AZ. Best, -jay ___ Mailing list:

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

Yeah, was thinking more of technically vs policy. Wondering if there are other dependencies or if I could patch this into a Liberty code base. On Wed, Jun 15, 2016 at 12:38 PM Jay Pipes wrote: > On 06/15/2016 03:58 AM, Paul Michali wrote: > > Awesome Jay! > > > > Do you

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

On 6/15/2016 10:30 AM, Daniel P. Berrange wrote: On Wed, Jun 15, 2016 at 03:19:28PM +, Jesse Keating wrote: I'll offer a counter point. We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping over Liberty. The database migrations to get from Kilo to Mitaka have ran

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

+1 Finally! On Wed, Jun 15, 2016 at 3:33 AM, Ihor Dvoretskyi wrote: > +1 for Alexander Tivelkov. > > Good effort. > > On Wed, Jun 15, 2016 at 1:08 PM, Artem Silenkov > wrote: > >> Hello! >> >> +1 >> >> Regards, >> Artem Silenkov >> --- >>

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

On 06/15/2016 03:58 AM, Paul Michali wrote: Awesome Jay! Do you think this is something that can be backporting to Liberty w/o other dependencies? We're running Liberty on our system right now. Doubtful, Paul :( The policy for upstream is not to backport feature patches. This would be

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Amrith Kumar wrote: Thanks for writing this up and for the interesting discussion that has come up in this ML thread. While I think I get the general idea of the motivation, I think the verbiage doesn't quite do justice to your intent. One area which I would like to highlight is the

[openstack-dev] [nova][cinder] Integration testing for Nova API os-assisted-volume-snapshots

In the nova-api meeting today we were talking about the nova os-assisted-volume-snapshots API and whether or not it was a proxy API to cinder. We determined it's not, it performs an action on a server resource. But what a few of us didn't realize was it's an admin API in nova only for cinder

Re: [openstack-dev] [neutron][ovs] The way we deal with MTU

First, some context: we talked it thru with Eugene on IRC, and Eugene reported that he cannot reproduce the issue on his setup using Ubuntu hypervisor with ovs 2.4: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2016-06-13.log.html#t2016-06-13T19:45:22 So I

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

On Wed, Jun 15, 2016 at 03:19:28PM +, Jesse Keating wrote: > I'll offer a counter point. > > We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping > over Liberty. > > The database migrations to get from Kilo to Mitaka have ran smoothly for us. While it is great

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

I'll offer a counter point.   We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping over Liberty.   The database migrations to get from Kilo to Mitaka have ran smoothly for us.   https://github.com/blueboxgroup/ursula/blob/master/upgrade.yml -jlk     - Original message

Re: [openstack-dev] [Octavia] [lbaas] Mid-Cycle proposed for the week of August 22nd

For most of the mid cycles we've set up some video conferencing for remote people to participate. I'll add a new section in the etherpad for remote people so we can set up all that information in one location. -Trevor From: Nir Magnezi

Re: [Openstack-operators] Mid-Cycle Ops Meetup venue choice - please make your voice heard!

Hi Saverio, I just checked my calendar and it seems that if a strong preference for one of the venues emerges by next Tuesday, we may be able to lock in that venue in time, since if that happens, there will be plenty of time (more than 8 weeks) after that decision for obtaining a visa. I hope

[Openstack] Restore nova instances after Ceph crash

Hi, this is no question for you guys, it's more of an information what I was facing today and I wanted to share it if any of you should be facing the same or similar issue. Due to an incautious upload of several huge images to glance (backed by Ceph) my colleague crashed our Ceph

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Thierry, Thanks for writing this up and for the interesting discussion that has come up in this ML thread. While I think I get the general idea of the motivation, I think the verbiage doesn't quite do justice to your intent. One area which I would like to highlight is the situation with the

Re: [openstack-dev] [ceilometer] [stable] Re: [Openstack-stable-maint] Stable check of openstack/ceilometer failed

  -Original Message- From: gordon chung Reply: gordon chung Date: June 14, 2016 at 21:14:17 To: Ian Cordasco , OpenStack Development Mailing List (not for usage questions) Subject:  Re:

[openstack-dev] [Nova] Virt device role tagging for other virt drivers

Hey folks, For a while now we've been working on virt device role tagging. The full spec is here [1], but the quick gist of it is that device tagging is a way for the user to assign arbitrary string tags to either vNICs or block devices. Those tags then get exposed by the metadata API to the

Re: [Openstack] Nova and Magnum on the same host?

On Jun 9, 2016, at 11:55 AM, Ricardo Carrillo Cruz wrote: > https://wiki.openstack.org/wiki/Docker I'm trying this and although I know very little of OS (and I haven't managed to boot up my first container yet because of other issues), I have the docker entry in the web GUI "Admin -> System ->

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On Tue, Jun 14, 2016 at 9:15 AM, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2016-06-14 15:57:10 +0200: >> Hi everyone, >> >> I just proposed a new requirement for OpenStack "official" projects, >> which I think is worth discussing beyond the governance

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 15, 2016, at 8:01 AM, Sean Dague wrote: > > On 06/15/2016 12:14 AM, Mark Voelker wrote: > >> >> It is perhaps important to note here that the DefCore seems to have two >> meanings to a lot of people I talk to today: it’s a mark of interoperability >> (the OpenStack

Re: [Openstack] load balancer using iptables rules in neutron

On 06/15/2016 12:18 AM, Priyanka wrote: Hi, I want to create a basic round-robin layer 3 load balancer. The request would be coming from same tenant network and the backend servers would also be in the same network. For this the steps I think should be done are: create a neutron port (for the

Re: [openstack-dev] [release][infra] networking-onos 2.0.0 not on our pypi mirrors

Excerpts from mohammad shahid's message of 2016-06-15 16:32:10 +0530: > Hi, > > Can someone look at this networking-onos 2.0.0 not on our pypi please ? > > reference links: > https://launchpad.net/networking-onos > https://pypi.python.org/pypi/networking-onos > > > Thanks and Regards, >

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

Excerpts from Chris Hoge's message of 2016-06-14 16:37:06 -0700: > Top posting one note and direct comments inline, I’m proposing > this as a member of the DefCore working group, but this > proposal itself has not been accepted as the forward course of > action by the working group. These are my

Re: [openstack-dev] [cinder]The backend-group concept in Cinder

You can define several backends with the same volume_backend_name and call that a group. For example: [groupA-be1] volume_backend_name=fast-ssd [groupA-be2] volume_backend_name=fast-ssd [groupB-be3] volume_backend_name=slow-disk So, no matter what storage is behind every backend, it will be

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

Hi John, I update the networking-sfc and networking-ovn for the new schema. I think the most important now is nail down the ovsdb schema for SFC, as you know, it is not hard to implement networking-sfc and networking-ovn, but if the schema changes, we have to update networking-sfc and

Re: [OpenStack-Infra] Request help for ICLA error

On 06/15/2016 12:58 PM, Soffie Huang wrote: > Hello Infra Team, > > I am trying to push the code changes for sanbox. But while initiating the > review I am getting the following Error. > > --- > fatal: ICLA contributor agreement requires current contact information. >

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Neil, On Wed, Jun 15, 2016 at 3:17 AM, Neil Jerram wrote: > On Wed, Jun 15, 2016 at 9:52 AM Thierry Carrez > wrote: >> >> [...] >> Those are good points. Note that I do not advocate for those projects to >> be kept closed/private: I'm simply saying that

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 06/15/2016 12:14 AM, Mark Voelker wrote: > > It is perhaps important to note here that the DefCore seems to have two > meanings to a lot of people I talk to today: it’s a mark of interoperability > (the OpenStack Powered badge that says certain capabilities of this cloud > behave like

[Openstack-operators] Issue running Controllers as virtual machines on Vmware hosts

Hi all, I'm trying to virtualize some controllers on Vmware hosts, however I have an issue with networking. When tripleo enables promiscuous mode on the interfaces inside the VM operating system, I lose connectivity to the network. I already permitted promiscuous mode on vmware vswitch. Anyone

[openstack-dev] [release][infra] networking-onos 2.0.0 not on our pypi mirrors

Hi, Can someone look at this networking-onos 2.0.0 not on our pypi please ? reference links: https://launchpad.net/networking-onos https://pypi.python.org/pypi/networking-onos Thanks and Regards, Mohammad Shahid __

[OpenStack-Infra] Request help for ICLA error

Hello Infra Team, I am trying to push the code changes for sanbox. But while initiating the review I am getting the following Error. --- fatal: ICLA contributor agreement requires current contact information. Please review your contact information:

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

Awesome Jay! Do you think this is something that can be backporting to Liberty w/o other dependencies? We're running Liberty on our system right now. On Tue, Jun 14, 2016 at 4:10 PM Jay Pipes wrote: > On 06/14/2016 12:30 PM, Paul Michali wrote: > > Well, looks like we

[Openstack] Devstack Auth Error in Neutron

Hi I have a devstack running on ubuntu LTS 14.04 and trying to setup lbaas setup using the url as below:- https://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRun But getting error as below when trying to create vip using neutron lbaas-loadbalancer-create --name lb1 private-subnet *An auth

Re: [openstack-dev] [Octavia] [lbaas] Mid-Cycle proposed for the week of August 22nd

Hi Michael, Will there be an option to participate from remote? Thanks, Nir On Fri, Jun 10, 2016 at 1:51 AM, Michael Johnson wrote: > Just a reminder, we have a proposed mid-cycle meeting set for the week > of August 22nd in San Antonio. > > If you would like to attend

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

+1 for Alexander Tivelkov. Good effort. On Wed, Jun 15, 2016 at 1:08 PM, Artem Silenkov wrote: > Hello! > > +1 > > Regards, > Artem Silenkov > --- > paas-team > > On Wed, Jun 15, 2016 at 12:56 PM, Dmytro Dovbii > wrote: > >> +1 >> 15 июня 2016 г.

Re: [OpenStack-Infra] Error with 'git review'

On 06/15/2016 12:21 PM, zhaolihuisky wrote: > Hi, all > > I commit the code using 'git review' command, but error happened. > > """ > $ git review > fatal: remote error: > ICLA contributor agreement requires current contact information. > > Please review your contact information: > >

Re: [openstack-dev] [kolla] Stability and reliability of gate jobs

Hi David, I agree with this completely. Gates continue to be a problem for Kolla, reasons why have been discussed in the past but at least for me it's not clear what the key issues are. I've added this item to agenda for todays IRC meeting (16:00 UTC -

[OpenStack-Infra] Error with 'git review'

Hi, all I commit the code using 'git review' command,  but error happened. """$ git reviewfatal: remote error:  ICLA contributor agreement requires current contact information. Please review your contact information:   https://review.openstack.org/#/settings/contact""; Then visit  

Re: [openstack-dev] [nova] Virtuozzo (Compute) CI is incorrectly patching for resize support

Hello, Matt! First of all, I want to apologize for the inconvenience. This all started yesterday when I updated Virtuozzo CI using latest puppets, Zuul, Jenkins and other stuff. The update somehow led to Zuul not passing environment variables like ZUUL_CHANGE, LOG_PATH to Jenkins job.

  1   2   >