We are tickled pink to announce the release of:
oslo.privsep 1.12.0: OpenStack library for privilege separation
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.privsep
With package available at:
https://pypi.pyt
1) Roll Call
2) OPNFV CI Evolution Study Progress
3) Bare Metal Deployment(PXE/IPMI) Status Update
4) Daisy Bare Metal Related DB Deployment Status Update
5) Bifrost/Ironic Integration
B.R.,
Zhijiang
__
OpenStack Developmen
Ravi:
If you only want to let the VM-SF to forward traffic from p2 to p3, you
can enable ip_forward in VM-SF and configure two static route in VM-SF.
Eg :ip route add VM-DST dev p2
ip route add VM-SRC dev p1
Jim
2016-08-18 8:02 GMT+08:00 Ravi Sekhar Reddy Konda <
ravisekhar.ko...@o
Hi Nikolas,
First of all, neutron-...@lists.opendaylight.org (copied) might be a
better place to ask networking-odl questions.
It seems that the external network you described is not managed by
OpenDaylight, so it failed port binding.
You probably want to configure multiple mechanism driver
On 17/08/16 15:46, Jiří Stránský wrote:
> On 16.8.2016 21:08, Brad P. Crochet wrote:
>> Hello TripleO-ians,
>>
>> I've started to look again at the introduced, but unused/undocumented
>> upgrade commands. It seems to me that given the current state of the
>> upgrade process (at least from Liberty -
Hi Ravi ,
I would suggest ,
[1] Use Ubuntu cloud images from "
http://cloud-images.ubuntu.com/trusty/current/"; , so you can do ssh login
and enable ipv4 forwarding by changing "net.ipv4.ip_forward = 1" in file
/etc/sysctl.conf
[2] In case of basic cirros image please add some static route as
Hi Magnum folks,
I have some interests in our auto scaling features and currently testing with
some container monitoring solutions such as heapster, telegraf and prometheus.
I have seen the PoC session corporate with Senlin in Austin and have some
questions regarding of this design:
- We have d
On 08/18/2016 09:29 AM, Marios Andreou wrote:
> On 17/08/16 15:46, Jiří Stránský wrote:
>> On 16.8.2016 21:08, Brad P. Crochet wrote:
>>> Hello TripleO-ians,
>>>
>>> I've started to look again at the introduced, but unused/undocumented
>>> upgrade commands. It seems to me that given the current sta
> On 18 Aug 2016, at 09:56, hie...@vn.fujitsu.com wrote:
>
> Hi Magnum folks,
>
> I have some interests in our auto scaling features and currently testing with
> some container monitoring solutions such as heapster, telegraf and
> prometheus. I have seen the PoC session corporate with Senlin i
2016-08-13 7:36 GMT+09:00 Anne Gentle :
>
>
> On Fri, Aug 12, 2016 at 3:29 AM, Akihiro Motoki wrote:
>>
>> this mail focuses on neutron-specific topics. I dropped cinder and ironic
>> tags.
>>
>> 2016-08-11 23:52 GMT+09:00 Anne Gentle :
>> >
>> >
>> > On Wed, Aug 10, 2016 at 2:49 PM, Anne Gentle
>
> > Currently, I saw that Magnum only send CPU and Memory metric to Ceilometer,
> > and Heat can grab these to decide the right scaling method. IMO, this
> > approach have some problems, please take a look and give feedbacks:
> > - The AutoScaling Policy and AutoScaling Resource of Heat cannot ha
hi, all.
Currently, there is no "rejoin-stack.sh" script in devstack.
It will clear all resources and create all resources if I rerun
"./stack.sh" after restarting system.
So, how to start all OpenStack services after restarting system
quickly?
Thanks
Zhi Chang
_
Hi Zhi,
Use "screen -c stack-screenrc" this will take you to the services screen.
On Thu, Aug 18, 2016 at 3:03 PM, zhi wrote:
> hi, all.
>
> Currently, there is no "rejoin-stack.sh" script in devstack.
>
> It will clear all resources and create all resources if I rerun
> "./stack.sh" a
The attached script is something I’ve used for a while and it works pretty
well. It does a little more than just the screen reconnection, it also gets you
the swift/cinder volumes that you’ll need if you want to run, say Trove.
-amrith
From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Hello all,
We need to decide on the number of rooms we need for the design summit.
I have started the below etherpad so we can all brainstorm the sessions we
would like
to conduct (and who is going to chair them):
https://etherpad.openstack.org/p/kuryr-barcelona
(For the Austin summit we had 1 f
Hi Yujun,
You understood correctly. ‘name’ is checked if it exists, and is ignored
otherwise.
Best Regards,
Ifat.
From: Yujun Zhang
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, 17 August 2016 at 18:01
To: "OpenStack Development Mailing List (not for
Team,
Thierry sent an email to all PTLs about space needs for next Summit.
Here's what we can have:
* Fishbowl sessions (from Wednesday 4pm to Friday noon)
Our traditional largish rooms organized in fishbowl style, with
advertised session content on the summit schedule for increased external
par
On Thu, Aug 18, 2016 at 3:33 AM, Akihiro Motoki wrote:
> 2016-08-13 7:36 GMT+09:00 Anne Gentle :
> >
> >
> > On Fri, Aug 12, 2016 at 3:29 AM, Akihiro Motoki
> wrote:
> >>
> >> this mail focuses on neutron-specific topics. I dropped cinder and
> ironic
> >> tags.
> >>
> >> 2016-08-11 23:52 GMT+09
Hi Neutron team,
As you may know, the OpenStack API references have been moved into
individual project repositories, but it contains a lot of wrong
information now :-(
Let's clean up API reference.
It's now time to start the clean up and finish the cleanup by Newton-1.
I prepared the etherpad pa
On 08/18/2016 08:16 AM, Akihiro Motoki wrote:
> Hi Neutron team,
>
> As you may know, the OpenStack API references have been moved into
> individual project repositories, but it contains a lot of wrong
> information now :-(
>
> Let's clean up API reference.
> It's now time to start the clean up a
Hello,
I just subscribed this list, usually I am on the operators list.
I have been reading the archives of this list:
http://lists.openstack.org/pipermail/openstack-dev/2016-June/097947.html
I am more than happy to hear that packages will be built in the
Openstack infra. Are we going to be able
Hey team,
Like other teams, we need to decide how many fishbowl, workroom, etc we
need.
Last time in Austin we had:
- 2 fishbowls
- 7 workroom
- Half a day of a contributors meetup (which IIRC got more or less
cancelled?)
Many of the sessions were empty and short, so I'd suggest to limit
ourse
Hi,
So in the first place, you do not need the multiple foreign keys in Flavor db
use case.
You can only declare flavor_id and service_profile_id in
FlavorServiceProfileBinding object, since the relationships ('flavor' and
'service_profile') is not used anywhere, only ids.
Secondly, nobody rig
The release team has prepared a proposed schedule for the Ocata cycle.
Please look over https://review.openstack.org/357214 and let us know if
you spot any issues.
Doug
__
OpenStack Development Mailing List (not for usage que
Hi Yujun,
This is something that we need to handle. You can open a bug about it.
Best Regards,
Ifat.
From: Yujun Zhang
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, 17 August 2016 at 07:08
To: "OpenStack Development Mailing List (not for usage question
Fix proposed in https://review.openstack.org/#/c/356974/
To enable validation of definition content, I have also made a refactoring
to the validator as in https://review.openstack.org/#/c/356947/
--
Yujun
On Wed, Aug 17, 2016 at 10:29 PM Har-Tal, Liat (Nokia - IL) <
liat.har-...@nokia.com> wrote
On Thu, Aug 18, 2016 at 4:25 AM, mathieu bultel wrote:
> On 08/18/2016 09:29 AM, Marios Andreou wrote:
>> On 17/08/16 15:46, Jiří Stránský wrote:
>>> On 16.8.2016 21:08, Brad P. Crochet wrote:
Hello TripleO-ians,
I've started to look again at the introduced, but unused/undocumented
Hi everyone,
Today we started getting CI feedback for all our (OpenStack-Ansible) patches
from DSS Cinder CI which always immediately fail. I expect
this may be because they’re in the process of getting setup and are supposed to
be targeting cinder repositories.
We would appreciate it if the
This is just a heads up that I'm out on vacation next week. I'll have my
laptop with me and probably checking email sporadically, but hope not
too all that much.
Dan Smith has graciously agreed to back me up next week so if there are
questions about anything related to the release please get w
On Thu, Aug 18, 2016 at 7:14 AM, Jesse Pretorius
wrote:
> Hi everyone,
>
> Today we started getting CI feedback for all our (OpenStack-Ansible) patches
> from DSS Cinder CI which always immediately fail. I
> expect this may be because they’re in the process of getting setup and are
> supposed to
On Thu, Aug 18, 2016 at 7:30 AM, Elizabeth K. Joseph
wrote:
> On Thu, Aug 18, 2016 at 7:14 AM, Jesse Pretorius
> wrote:
>> Hi everyone,
>>
>> Today we started getting CI feedback for all our (OpenStack-Ansible) patches
>> from DSS Cinder CI which always immediately fail. I
>> expect this may be
Hey everybody,
As you all know, voting is only one step in the selection process. We
also have to have vetting done on the choices to identify risk
associated with the selected names.
This time around, the top choice by vote for both P and Q was too
problematic, so we moved down to the next most
It's that time of year again to talk about killing this job, at least
from the integrated gate (move it to experimental for people that care
about postgresql, or make it gating on a smaller subset of projects like
oslo.db).
The postgresql job used to have three interesting things about it:
1.
On 16-08-18 10:59 AM, Monty Taylor wrote:
Hey everybody,
As you all know, voting is only one step in the selection process. We
also have to have vetting done on the choices to identify risk
associated with the selected names.
This time around, the top choice by vote for both P and Q was too
pro
On Thu, Aug 18, 2016 at 07:57:25AM -0700, Elizabeth K. Joseph wrote:
> On Thu, Aug 18, 2016 at 7:30 AM, Elizabeth K. Joseph
> wrote:
> > On Thu, Aug 18, 2016 at 7:14 AM, Jesse Pretorius
> > wrote:
> >> Hi everyone,
> >>
> >> Today we started getting CI feedback for all our (OpenStack-Ansible)
>
These changes are necessary so policy files can in include the check
"is_admin_project:True" which allows us to Scope what is meant by "Admin"
Use from_environ to load context
Use to_policy_values for enforcing policy
Use context from_environ to load contexts
Use from_dict to load context p
The agenda [1] for today's meeting has no items, so I'm calling it for the
meeting this week.
Please review your action items from last meeting and update the ML if you
haven't done so already
romcheg to annouunce fuel2 promotion and old fuel CLI removal on ML
akscram to send ML about moving clus
On Thu, Aug 18, 2016 at 03:44:10AM +, Husheng (TommyLike, R&D IT&Tools
Equipment Dept) wrote:
> Hi all,
> Sorry for absence from IRC meeting of this week and put forward this topic on
> driver deprecation policy again. Actually I support the driver support tag
> policy completely, it's a rea
Reported at https://bugs.launchpad.net/vitrage-dashboard/+bug/1614585
--
Yujun
On Thu, Aug 18, 2016 at 9:44 PM Afek, Ifat (Nokia - IL)
wrote:
> Hi Yujun,
>
> This is something that we need to handle. You can open a bug about it.
>
> Best Regards,
> Ifat.
>
> From: Yujun Zhang
> Reply-To: "OpenSt
Hi,
https://review.openstack.org/#/c/327112/ targets the parameter verification for
servers-actions.inc.
Br,
Gerg0
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: Thursday, August 18, 2016 2:33 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [n
I guess the intent was to indicate the need for indicating the micro or
in case of Glance minor version bump when required.
The API isn't drastically different, there are new and old elements as
shown in the Nova api ref linked.
On 8/12/16 5:49 AM, Sean Dague wrote:
> On 08/11/2016 06:02 PM, Bria
Major,
This makes perfect sense and will fit well into the work my team is already
doing on RHEL7 STIG hardening and will allow us to easily upstream our work.
Regards
MH
-Original Message-
From: Major Hayden [mailto:ma...@mhtx.net]
Sent: Friday, August 12, 2016 10:39 AM
To: openstack-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/18/2016 11:26 AM, Hooper, Mark (Nokia - US) wrote:
> This makes perfect sense and will fit well into the work my team is already
> doing on RHEL7 STIG hardening and will allow us to easily upstream our work.
Thanks for the input, Mark! :)
-
On 08/18/2016 10:00 AM, Matt Riedemann wrote:
> It's that time of year again to talk about killing this job, at least
> from the integrated gate (move it to experimental for people that care
> about postgresql, or make it gating on a smaller subset of projects like
> oslo.db).
>
> The postgresql j
+1
Vikas has been working on various aspects of Kuryr with dedication for some
time. So yes it's about time :)
Best,
Mohammad
From: Antoni Segura Puimedon
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 08/16/2016 05:55 PM
Subject:[opens
On Thu, Aug 18, 2016 at 11:33:59AM -0500, Matthew Thode wrote:
> On 08/18/2016 10:00 AM, Matt Riedemann wrote:
> > It's that time of year again to talk about killing this job, at least
> > from the integrated gate (move it to experimental for people that care
> > about postgresql, or make it gating
On 08/18/2016 11:57 AM, Nikhil Komawar wrote:
> I guess the intent was to indicate the need for indicating the micro or
> in case of Glance minor version bump when required.
>
> The API isn't drastically different, there are new and old elements as
> shown in the Nova api ref linked.
Right, so th
Greetings OpenStack community,
Today's open discussion centered around the concept of capabilities and
the need to ensure that however we end up doing them in APIs there
should be consistency amongst the existing OpenStack services. In fact,
it would be great if there were consistency between
Focus
-
We're approaching feature freeze deadline so teams should be wrapping
up feature development as we approach the final milestone 29 Aug -
2 Sept.
General Notes
-
The upcoming third milestone marks the start of several freezes in
our release cycle to let us shift our focus
Concrete example of an api-ref difference between Mitaka and Newton:
https://review.openstack.org/#/c/356693/1/api-ref/source/v2/images-parameters.yaml
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: Thursday, August 18, 2016 10:20 AM
To: Nikhil Komawar ; OpenStack Devel
I followed the instructions from IBM and Swift does appear to work
correctly under mod_wsgi. I have yet to do extensive multi-node testing.
I'm a bit surprised why those, ~50 SLOC code snippets to start the service,
have yet to be integrated into the Swift repo.
In my single node environment, Gla
We are overjoyed to announce the release of:
stevedore 1.17.1: Manage dynamic plugins for Python applications
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/stevedore
With package available at:
https://pypi.python.o
We are amped to announce the release of:
glance_store 0.17.0: OpenStack Image Service Store Library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/glance_store
With package available at:
https://pypi.python.org/pypi
We are joyful to announce the release of:
tooz 1.43.0: Coordination library for distributed systems.
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/tooz
With package available at:
https://pypi.python.org/pypi/tooz
We are grateful to announce the release of:
futurist 0.18.0: Useful additions to futures, from the future.
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/futurist
With package available at:
https://pypi.python.org/p
We are joyful to announce the release of:
oslotest 2.9.0: Oslo test framework
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslotest
With package available at:
https://pypi.python.org/pypi/oslotest
Please report i
We are delighted to announce the release of:
oslo.versionedobjects 1.16.0: Oslo Versioned Objects library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.versionedobjects
With package available at:
https://pypi.
We are eager to announce the release of:
oslo.log 3.15.0: oslo.log library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.log
With package available at:
https://pypi.python.org/pypi/oslo.log
Please report issu
We are satisfied to announce the release of:
taskflow 2.6.0: Taskflow structured state management library.
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/taskflow
With package available at:
https://pypi.python.org/p
We are high-spirited to announce the release of:
oslo.context 2.9.0: Oslo Context library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.context
With package available at:
https://pypi.python.org/pypi/oslo.cont
We are excited to announce the release of:
oslo.concurrency 3.14.0: Oslo Concurrency library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.concurrency
With package available at:
https://pypi.python.org/pypi/os
We are mirthful to announce the release of:
oslo.cache 1.13.0: Cache storage for Openstack projects.
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.cache
With package available at:
https://pypi.python.org/pypi/
On 08/17/2016 03:52 PM, Nick Papadonis wrote:
> Comments
>
>
> Glance worked for me in Mitaka. I had to specify 'chunked transfers'
> and increase the size limit to 5GB. I had to pull some of the WSGI
> source from glance and alter it slightly to call from Apache.
>
> I saw that Nova claims mo
We are glad to announce the release of:
oslo.db 4.12.0: Oslo Database library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.db
With package available at:
https://pypi.python.org/pypi/oslo.db
Please report iss
We are overjoyed to announce the release of:
oslo.config 3.16.0: Oslo Configuration API
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.config
With package available at:
https://pypi.python.org/pypi/oslo.config
We are glowing to announce the release of:
oslo.middleware 3.18.0: Oslo Middleware library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.middleware
With package available at:
https://pypi.python.org/pypi/oslo.
We are frolicsome to announce the release of:
oslo.messaging 5.8.0: Oslo Messaging API
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.messaging
With package available at:
https://pypi.python.org/pypi/oslo.messa
We are grateful to announce the release of:
oslo.i18n 3.9.0: Oslo i18n library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.i18n
With package available at:
https://pypi.python.org/pypi/oslo.i18n
Please repor
On 08/18/2016 10:00 AM, Matt Riedemann wrote:
> It's that time of year again to talk about killing this job, at least
> from the integrated gate (move it to experimental for people that care
> about postgresql, or make it gating on a smaller subset of projects like
> oslo.db).
>
> The postgresql j
We are stoked to announce the release of:
python-novaclient 5.1.0: Client library for OpenStack Compute API
This release is part of the newton release series.
With source available at:
https://git.openstack.org/cgit/openstack/python-novaclient
With package available at:
https://pypi.p
On 08/18/2016 11:00 AM, Matt Riedemann wrote:
> It's that time of year again to talk about killing this job, at least
> from the integrated gate (move it to experimental for people that care
> about postgresql, or make it gating on a smaller subset of projects like
> oslo.db).
>
> The postgresql j
On 8/18/2016 12:14 PM, Matthew Treinish wrote:
On Thu, Aug 18, 2016 at 11:33:59AM -0500, Matthew Thode wrote:
On 08/18/2016 10:00 AM, Matt Riedemann wrote:
It's that time of year again to talk about killing this job, at least
from the integrated gate (move it to experimental for people that car
i'm cool with less space requirements. as the summit is basically all marketing
driven now, i don't see any increase in devs being sent to Barcelona.
do we even want the contributors meetup? based on last few summits, a good
chunk of people just choose to fly out on the last day so basically no
Excerpts from Matthew Thode's message of 2016-08-18 13:18:05 -0500:
> On 08/18/2016 10:00 AM, Matt Riedemann wrote:
> > It's that time of year again to talk about killing this job, at least
> > from the integrated gate (move it to experimental for people that care
> > about postgresql, or make it g
its fine from what i can tell although i don't see the udp publishing you
mentioned... and you are using a common pollster so i'm not sure what vsg
meter. based on what you pasted, it's probably the kafka publisher.
On 18/08/16 01:37 AM, Raghunath D wrote:
Hi Gordon,
Did you get a chance to loo
We have a lot of open changes for the centralize / cleanup config option
work:
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/centralize-config-options-newton
We said at the midcycle we'd allow those past non-priority feature
freeze because they are
On 8/18/2016 1:18 PM, Matthew Thode wrote:
Perhaps a better option would be to get oslo.db to run cross-project
checks like we do in requirements. That way the right team is covering
the usage of postgres and we still have coverage while still lowering
gate load for most projects.
___
Roger that.
On 08/18/2016 11:48 AM, Matt Riedemann wrote:
We have a lot of open changes for the centralize / cleanup config option
work:
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/centralize-config-options-newton
We said at the midcycle we'd all
> -Original Message-
> From: hie...@vn.fujitsu.com [mailto:hie...@vn.fujitsu.com]
> Sent: August-18-16 3:57 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [Magnum] Next auto-scaling feature design?
>
> Hi Magnum folks,
>
> I have some interests in our auto scaling
On 08/18/2016 01:50 PM, Matt Riedemann wrote:
> On 8/18/2016 1:18 PM, Matthew Thode wrote:
>> Perhaps a better option would be to get oslo.db to run cross-project
>> checks like we do in requirements. That way the right team is covering
>> the usage of postgres and we still have coverage while sti
Hey, OpenStackers!
recently I've got lots comments about current time our Performance Team
meetings are held on. Right now we're having them 16:00 UTC on Tuesdays
(9:00 PST) (#openstack-performance IRC channel) and this time slot is not
that much comfortable for some of the US folks due to interna
On 08/18/2016 03:31 PM, Matthew Thode wrote:
> On 08/18/2016 01:50 PM, Matt Riedemann wrote:
>> On 8/18/2016 1:18 PM, Matthew Thode wrote:
>>> Perhaps a better option would be to get oslo.db to run cross-project
>>> checks like we do in requirements. That way the right team is covering
>>> the usa
Tatiana,
Thanks for filing the bug and putting in a patch!
Cheers,
Praveen
On Wed, Aug 17, 2016 at 1:45 AM Tatiana Ovtchinnikova <
t.v.ovtchinnik...@gmail.com> wrote:
> Filed a bug: https://bugs.launchpad.net/horizon/+bug/1614000
>
>
> 2016-08-17 11:19 GMT+03:00 Tatiana Ovtchinnikova <
> t.v.ovtc
On Fri, Aug 19, 2016 at 1:00 AM, Matt Riedemann
wrote:
> It's that time of year again to talk about killing this job, at least from
> the integrated gate (move it to experimental for people that care about
> postgresql, or make it gating on a smaller subset of projects like oslo.db).
>
> The post
We're still ok with merging existing ones though?
Michael
On Fri, Aug 19, 2016 at 5:18 AM, Jay Pipes wrote:
> Roger that.
>
> On 08/18/2016 11:48 AM, Matt Riedemann wrote:
>
>> We have a lot of open changes for the centralize / cleanup config option
>> work:
>>
>> https://review.openstack.org/#
On 08/18/2016 04:46 PM, Michael Still wrote:
> We're still ok with merging existing ones though?
Mostly we'd like to conserve the CI time now. It's about 14.5 node-hours
to run CI on these patches (probably on about 9 node-hours in the gate).
With ~800 nodes every patch represents 1.5% of our CI r
On 08/18/2016 02:22 PM, Sean Dague wrote:
> On 08/18/2016 11:00 AM, Matt Riedemann wrote:
>> It's that time of year again to talk about killing this job, at least
>> from the integrated gate (move it to experimental for people that care
>> about postgresql, or make it gating on a smaller subset of
Hey,
Thanks for the answer. It might be that I did not fully understand the
networking concept here.
OVS on the host node-3 is as well controlled by opendaylight. And opendaylight
sets up the external network as well. But it is still a flat network without
segmentation. As far as I understood
We have had numerous discussion on this topic, including a presentation and
a design session
in Tokyo, but we have not really arrived at a consensus yet. Part of the
problem is that auto-scaling
at the container level is still being developed, so it is still a moving
target.
However, a few point
Hey team,
I need to let folks know what we would like for rooms in Barcelona. This
is always the tricky part of guesstimating what we will need by then.
I'll bring this up in next week's meeting to discuss, but I wanted to
get it out there so everyone could start thinking about it now.
In Austin
On 8/18/2016 3:44 PM, Michael Still wrote:
On Fri, Aug 19, 2016 at 1:00 AM, Matt Riedemann
mailto:mrie...@linux.vnet.ibm.com>> wrote:
It's that time of year again to talk about killing this job, at
least from the integrated gate (move it to experimental for people
that care about pos
On Thu, Aug 18, 2016 at 02:44:47PM +0200, Saverio Proto wrote:
> Hello,
>
> I just subscribed this list, usually I am on the operators list.
>
> I have been reading the archives of this list:
> http://lists.openstack.org/pipermail/openstack-dev/2016-June/097947.html
>
> I am more than happy to h
+1
On 18 August 2016 at 18:09, Steven Dake (stdake) wrote:
> Kolla Core Review Team:
>
> I am nominating Eduardo for the core reviewer team. His reviews are
> fantastic, as I'm sure most of you have seen after looking over the review
> queue. His 30 day stats place him at #3 by review count [1]
Hi,
we have a problem again with not enough memory in HA jobs, all of them
constantly fails in CI: http://status-tripleoci.rhcloud.com/
I've created a patch that will increase it[1], but we need to increase it
right now on rh1.
I can't do it now, because unfortunately I'll not be able to watch thi
Kolla Core Review Team:
I am nominating Eduardo for the core reviewer team. His reviews are fantastic,
as I'm sure most of you have seen after looking over the review queue. His 30
day stats place him at #3 by review count [1] and 60 day stats [2] at #4 by
review count. He is also first to r
Early planning is starting for the Ocata summit so I've started an
etherpad to dump ideas for sessions:
https://etherpad.openstack.org/p/ocata-nova-summit-ideas
The summit in Barcelona is 4 days, with ops and cross-project taking up
Tuesday and most of Wednesday. The Friday meetups will be in
On Tue, Aug 16, 2016 at 10:40:07PM +, Elancheran Subramanian wrote:
> Hello There,
> I’m currently playing with using Tempest as our integration tests for our
> internal and external clouds, facing some issues with api which are not
> supported in our cloud. For ex, listing domains isn’t supp
On Wed, Aug 17, 2016 at 12:27:29AM +, Elancheran Subramanian wrote:
> Hello Punal,
> We do support both V2 and V3, that’s just a example I’ve stated BTW. We do
> have our own integration tests which are pretty much covers all our
> integration points with openstack. But we would like to lever
On Thu, Aug 18, 2016 at 15:36:00PM +, Sean McGinnis
wrote:
> > Hi all,
> > Sorry for absence from IRC meeting of this week and put forward this topic
> > on driver deprecation policy again. Actually I support the driver support
> > tag policy completely, it's a reasonable policy for both si
Cloud you give me the output of `ovs-vsctl show` on node-3?
On 8/19/2016 5:20 AM, Nikolas Hermanns wrote:
Hey,
Thanks for the answer. It might be that I did not fully understand the
networking concept here.
OVS on the host node-3 is as well controlled by opendaylight. And opendaylight
sets up
1 - 100 of 103 matches
Mail list logo
