> On 11. May 2018, at 21:56, Remo Mattei wrote:
>
> I need windows 2016 and the cloudit has 2012.
>
> Thanks I will probably end up doing the iso.
Cloudbase offers the tool to build there Images on Github.
https://github.com/cloudbase/windows-openstack-imaging-tools
Hi Tushar,
Thanks for linking to that document, I hadn't seen it before and it's very
useful. As far as milestones are concerned, I was planning on sticking with
Pike. Up until this point I've been using the packages from
http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike
Hi Christian,
I have build it for the 2016 and it’s working now. I did not use the GitHub
below.
Remo
> On May 17, 2018, at 5:29 AM, Christian Berendt
> wrote:
>
>
>
>> On 11. May 2018, at 21:56, Remo Mattei wrote:
>>
>> I need windows
Hello - I'm trying to install a working local.conf devstack ocata on a
new server, and some python packages have changed so I end up with this
error during the build of octavia image:
2018-05-18 01:00:26.276 | Found existing installation: Jinja2 2.8
2018-05-18 01:00:26.280 |
2018-05-17 9:38 GMT+08:00 Alex Xu :
>
>
> 2018-05-17 1:24 GMT+08:00 Jay Pipes :
>
>> On 05/16/2018 01:01 PM, Nadathur, Sundar wrote:
>>
>>> Hi,
>>> The Cyborg quota spec [1] proposes to implement a quota (maximum
>>> usage) for accelerators on a
Hi,
An urgent matter has come up this week. If possible, can someone please replace
me.
Sorry
Gary
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Jeremy Stanley wrote:
[...]
As a community, we're likely to continue to make imbalanced
trade-offs against relevant security features if we don't move
forward and declare that some sort of standardized key storage
solution is a fundamental component on which OpenStack services can
rely. Being
Hello,
I was interested in getting Magnum working in gate by getting @dms patch
fixed and merged [1].
The installation goes fine on Ubuntu and CentOS however the tempest
testing for Magnum fails on CentOS (it not available in Ubuntu).
It seems to be related to authentication against keystone
On 05/17/2018 10:18 AM, Bogdan Dobrelya wrote:
> On 5/17/18 9:58 AM, Thierry Carrez wrote:
>> Jeremy Stanley wrote:
>>> [...]
>>> As a community, we're likely to continue to make imbalanced
>>> trade-offs against relevant security features if we don't move
>>> forward and declare that some sort
On 5/17/18 9:58 AM, Thierry Carrez wrote:
Jeremy Stanley wrote:
[...]
As a community, we're likely to continue to make imbalanced
trade-offs against relevant security features if we don't move
forward and declare that some sort of standardized key storage
solution is a fundamental component on
pycodestyle-2.4.0 added new warnings W605 and W606, which needs to be
addressed or future versions of python3 will refuse to run.
https://github.com/PyCQA/pycodestyle/pull/676
(OpenStack CI's flake8 is pre pycodestyle age, flake8 version isn't
managed by g-r, but that's another story. No release
Hi All,
As most of us will be in Vancouver summit next week, i am canceling
the next week QA office hour (24th May, Thursday).
We will resume the same after summit which will be on 31st May, Thursday.
-gmann
__
OpenStack
Hi All,
QA team is planning an onboarding session during the Vancouver Summit:
-
https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21646/qa-project-onboarding
- Tuesday, May 22, 2018, 9:50am-10:30am
- Vancouver Convention Centre West - Level Two - Room 223
Details of this
On 16.05.18 20:40, Doug Hellmann wrote:
Weren't the folks doing the training-labs or training-guides taking a
similar approach? IIRC, they ended up implementing what amounted to
their own installer for OpenStack, and then ended up with all of the
associated upgrade and testing burden.
Hi All,
Problem description:
Monty Taylor added split-logger functionality in patch[1].
This functionality splits logs in four different logs:
* keystoneauth.session.request
* keystoneauth.session.response
* keystoneauth.session.body
*
Hi all,
Some of the team will be attending the OpenStack summit in Vancouver,
so I am canceling the weekly IRC meeting for the 23rd.
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
__
OpenStack Development Mailing List
Hi,
unfortunately, didn't get the reply in my inbox, so I'm answering from the link
here:
http://lists.openstack.org/pipermail/openstack-operators/2018-May/015270.html
(hopefully, my reply will go to the same thread)
Anyway, I can see the neutron openvswitch agent logs processing the interface
On 05/17/2018 09:49 AM, Tobias Urdin wrote:
> Hello,
>
> I was interested in getting Magnum working in gate by getting @dms patch
> fixed and merged [1].
>
> The installation goes fine on Ubuntu and CentOS however the tempest
> testing for Magnum fails on CentOS (it not available in Ubuntu).
>
On 2018-05-17 16:09:12 +0900 (+0900), IWAMOTO Toshihiro wrote:
[...]
> OpenStack CI's flake8 is pre pycodestyle age,
It's not "OpenStack CI's flake8" version. Nova's master branch is
getting flake8 transitively through its test-requirement on
hacking!=0.13.0,<0.14,>=0.12.0 which is causing it to
Here is the countdown content for the next two weeks, to cover while the Summit
takes place.
Development Focus
-
Work on new features should be well underway. The Rocky-2 milestone is coming
up quick.
Hopefully teams have good representation attending the Forum. This is a great
On Wed, 16 May 2018 13:26:46 -0600
Wesley Hayutin wrote:
> On Wed, May 16, 2018 at 3:05 PM Doug Hellmann wrote:
>
> > Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600:
> > > On Wed, May 16, 2018 at 2:41 PM Doug Hellmann
We have other scheduled tests that perform end-to-end (assign floating IP,
ssh, ping outside) and never had an issue.
I think we turned it off because the callback code was initially buggy and
nova would wait forever while things were in fact ok, but I'll change
"vif_plugging_is_fatal = True" and
On 2018-05-17 16:35:36 +0200 (+0200), Petr Kovar wrote:
> On Wed, 16 May 2018 17:05:15 +
> Jeremy Stanley wrote:
>
> > On 2018-05-16 18:24:45 +0200 (+0200), Petr Kovar wrote:
> > [...]
> > > I'd like to propose replacing the reference to the IBM Style Guide
> > > with a
Hey Gary, my turn is coming up soon (week of June 4th), I can jump the line a bit and cover you if you or anyone can cover my currently assigned week.
Thanks,
- James Anziano
- Original message -From: Gary Kotton To: OpenStack List
Thanks!
From: James Anziano
Reply-To: OpenStack List
Date: Thursday, May 17, 2018 at 6:21 PM
To: OpenStack List
Cc: OpenStack List
Subject: Re: [openstack-dev]
After some discussion on twitter and IRC, we've added a new session to
the Forum schedule for next week to discuss our options for cleaning up
some of the design/technical debt in our REST APIs. It's early days in
the conversation, but we wanted to take advantage of our time together
in person to
We use "vif_plugging_is_fatal = False" and "vif_plugging_timeout = 0" as
well as "no-ping" in the dnsmasq-neutron.conf, and large rally tests of 500
instances complete with no issues.
These are some good blogposts about Neutron performance:
On 5/17/2018 9:46 AM, George Mihaiescu wrote:
and large rally tests of 500 instances complete with no issues.
Sure, except you can't ssh into the guests.
The whole reason the vif plugging is fatal and timeout and callback code
was because the upstream CI was unstable without it. The server
Hi All:
With the Summit at Vancouver, we will cancel the FWaaS weekly meeting for May
24 14:00 UTC. We will resume as usual from May 31.
Thanks
Sridar
__
OpenStack Development Mailing List (not for usage questions)
On Wed, 16 May 2018 17:05:15 +
Jeremy Stanley wrote:
> On 2018-05-16 18:24:45 +0200 (+0200), Petr Kovar wrote:
> [...]
> > I'd like to propose replacing the reference to the IBM Style Guide
> > with a reference to the developerWorks editorial style guide
> >
Doug Hellmann wrote on 05/14/2018 08:52:08 AM:
>
... snip ...
>
> We still have about 50 open patches related to adding the
> lower-constraints test job. I'll keep those open until the third
> milestone of the Rocky development cycle, and then abandon the rest to
> clear
On Thu, May 17, 2018 at 10:22 AM Petr Kovar wrote:
> On Wed, 16 May 2018 13:26:46 -0600
> Wesley Hayutin wrote:
>
> > On Wed, May 16, 2018 at 3:05 PM Doug Hellmann
> wrote:
> >
> > > Excerpts from Wesley Hayutin's message of
Greetings OpenStack community,
Today's meeting was brief, primarily focused on planning for the
summit sessions[7][8] that the SIG will host and facilitate.
The first session[7], will be a Birds of a Feather (BoF) gathering
where the topics will be determined by the attendees. One topic that
On 5/15/2018 3:48 AM, saga...@nttdata.co.jp wrote:
We store the service logs which are created by VM on that storage.
I don't mean to be glib, but have you considered maybe not doing that?
--
Thanks,
Matt
___
OpenStack-operators mailing list
There will be no Manila weekly meeting, Thursday May 24, given the
Vancouver Summit is going on that week.
-- Tom Barron
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Next week at the Summit there is a forum session dedicated to Manila
opertors' feedback on Thursday from 1:50-2:30pm [1] for which we have
started an etherpad [2]. Please come and help manila developers do
the right thing! We're particularly interested in experiences running
the OpenStack
Thierry Carrez [mailto:thie...@openstack.org]
>
> Graham Hayes wrote:
> > Any additional background on why we allowed LCOO to operate like this
> > would help a lot.
>
The group was started back when OPNFV was first getting involved with
OpenStack. Many of the members came from that
Hello,
Due to members attending the OpenStack summit in Vancouver, we will be
canceling the Security SIG meeting on May 24th.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 16/05/18 13:11, Ben Nemec wrote:
On 05/16/2018 10:39 AM, Petr Kovar wrote:
Hi all,
In the past few years, we've seen several efforts aimed at automating
procedural documentation, mostly centered around the OpenStack
installation guide. This idea to automatically produce and verify
On 5/17/2018 3:36 PM, Nadathur, Sundar wrote:
This applies only to the resources that Nova handles, IIUC, which does
not handle accelerators. The generic method that Alex talks about is
obviously preferable but, if that is not available in Rocky, is the
filter an option?
If nova isn't
On 5/17/2018 11:02 AM, Doug Hellmann wrote:
After some discussion on twitter and IRC, we've added a new session to
the Forum schedule for next week to discuss our options for cleaning up
some of the design/technical debt in our REST APIs.
Not to troll too hard here, but it's kind of
As majority of the team is in Vancouver for the summit we will cancel
next weeks meeting (24th of May). Glance team will have next meeting
in IRC Thu 31st.
Thanks,
Erno "jokke" Kuvaja
__
OpenStack Development Mailing List
CERN has upgraded to Cells v2 and is doing performance testing of the
scheduler and were reporting some things today which got us back to this
bug [1]. So I've starting pushing some patches related to this but also
related to an older blueprint I created [2]. In summary, we do quite a
bit of
Hi all,
Thanks for all the feedback. Please see below.
2018-05-17 1:24 GMT+08:00 Jay Pipes >:
Placement already stores usage information for all allocations of
resources. There is already even a /usages API endpoint that you can
CERN has upgraded to Cells v2 and is doing performance testing of the
scheduler and were reporting some things today which got us back to this
bug [1]. So I've starting pushing some patches related to this but also
related to an older blueprint I created [2]. In summary, we do quite a
bit of
Cross posting from Openstack-dev because Tom's unable to post to this
list yet. Manila operators, please note the session at the Forum next
week.
Thanks,
Goutham
-- Forwarded message --
From: Tom Barron
Date: Thu, May 17, 2018 at 10:57 AM
Subject:
Hi,
We are canceling our next Neutron Upgrades subteam meeting on May 24th, due to
summit.
We will resume on May 31st.
Thanks,
Lujin
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 2018-05-17 18:47:06 -0500 (-0500), Matt Riedemann wrote:
> On 5/17/2018 5:23 PM, Matt Riedemann wrote:
> > Not to troll too hard here, but it's kind of frustrating to see that
> > twitter trumps people actually proposing sessions on time and then
> > having them be rejected.
>
> I reckon this
On 5/17/2018 5:23 PM, Matt Riedemann wrote:
Not to troll too hard here, but it's kind of frustrating to see that
twitter trumps people actually proposing sessions on time and then
having them be rejected.
I reckon this is because there were already a pre-defined set of slots /
rooms for
Folks,
TL;DR
The last session related to extended releases is: OpenStack is "mature" -- time
to get serious on Maintainers
It will be in room 220 at 11:00-11:40
The etherpad for the last session in the series on Extended releases is here:
50 matches
Mail list logo