Count me in for Android beta testing.
On Sep 2, 2016 11:31 PM, "Jimmy McArthur" wrote:
>
> We're looking for a handful of community members to test our updated
OpenStack Summit mobile Apps. If you're interested, shoot me a note, along
with iOS/Android preference, and we'll get you set up.
>
> Tha
Hi Networking SFC team
I am trying out networking-SFC on the AllInOne Devstack(master branch) VM
brought up on the VirtualBox.
I am trying out the following scenario
|--| |--| |--|
| SRC-VM | | SF-VM | | DST-VM |
|--| |--| |--
Hello Clark,
Thanks!
I also had a look at the fix.
It eliminates 'stud' usage and replace it by apache2/mod_ssl, right?
But, there are use cases like:
- use apache2/mod_wsgi for better performance
and
- have an out-of-the-box SSL terminator (box)
Also, we have 'USE_TLS' option enabling t
Hi Jimmy,
I would like to vouch towards this effort. Could you tell me the next steps for
Android device?
Thanks,
Kaustubh
On Fri, Sep 2, 2016 at 1:59 PM -0400, "Jimmy McArthur"
mailto:ji...@openstack.org>> wrote:
We're looking for a handful of community members to test our updated
OpenSta
On 09/02/2016 12:40 PM, Eric Harney wrote:
On 08/15/2016 04:48 AM, Thierry Carrez wrote:
Sean Dague wrote:
On 08/12/2016 01:10 PM, Walter A. Boring IV wrote:
I believe there is a compromise that we could implement in Cinder that
enables us to have a deprecation
of unsupported drivers that aren
On Wed, Aug 31, 2016 at 12:48:42PM +1000, Tony Breeds wrote:
> Along with this being the Final release for client libraries freeze its also
> the requirements freeze.
>
> That means that on Thursday Sept 1st (UTC) we'll add a procedural -2 to all
> open changes in the master branch of openstack/r
>
> On 09/02/2016 01:53 PM, Doug Hellmann wrote:
>
>> Excerpts from Thierry Carrez's message of 2016-09-02 12:15:33 +0200:
>
> I agree with Sean: increasing the variety of technologies used increases
>>> the system complexity, which in turn requires more skills to fully
>>> understand and maintain
We are tickled pink to announce the release of:
os_vif 1.2.1: A library for plugging and unplugging virtual interfaces
in OpenStack.
This release is part of the newton stable release series.
With package available at:
https://pypi.python.org/pypi/os_vif
For more details, please see below.
Hello,
Here is an update on the issue of not being able to capture packets flowing
between two VMs on the same host.
Isolating the problem:
It has been confirmed that the TaaS OVS driver cannot capture packets
ingressing (flowing into) a VM's vNIC under the following conditions:
- The sender port
On Fri, Sep 2, 2016, at 10:50 AM, Masanori Itoh wrote:
> Hello,
>
> Recently, I noticed that on Ubuntu Xenial 'stud' for tls-proxy option
> is no longer available and replaced by 'hitch'.
>
> I filed a bug report and proposed a fix.
>
> https://bugs.launchpad.net/devstack/+bug/1613071
> https://
On 09/02/2016 01:53 PM, Doug Hellmann wrote:
Excerpts from Thierry Carrez's message of 2016-09-02 12:15:33 +0200:
Sean Dague wrote:
Putting DB trigger failure analysis into the toolkit required to manage
an upgrade failure is a really high bar for new ops.
I agree with Sean: increasing the
On 9/2/16, 8:48 AM, "Paul Bourke" wrote:
>Hi Kolla,
>
>We have been experiencing a long running issue with Kolla that I have
>brought up briefly a few times, but not made too much noise about.
>
>I'm taking the time to write about it in the hopes that a) as a
>community we may be able to s
We've discovered that the branching script had an overly restrictive
regex for detecting the URL to the upper contraints file, so some
repositories that have been branched and that use constraints did not
receive the update to use the version of the constraints in the
requirements stable branch.
Y
Shh! Let them get the leg irons welded shut on him first :-). Pay no
attention Ron... Congratulations!
Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet: bto...@us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680
From: Morgan Fainberg
To: "OpenSt
> On 02 Sep 2016, at 19:04, Jeffrey Zhang wrote:
>
> I think the right solution should warn the end-user: you need configure a
> large partition for /var/lib/docker.
Confirmed. The volumes of Mongodb and of Mariadb are getting pretty big as
well. Using /var/lib/nova (or /var/lib/mariadb, ..) o
On 9/1/2016 4:09 PM, Ildiko Vancsa wrote:
Hi All,
As we skipped a few meetings and we also reached the N-3 milestone this week I
would like to summarise where we are currently with our plans.
At the beginning of the Newton cycle we decided to refactor the Cinder API
around attach and detach
Le 02/09/2016 19:57, Jimmy McArthur a écrit :
We're looking for a handful of community members to test our updated
OpenStack Summit mobile Apps. If you're interested, shoot me a note,
along with iOS/Android preference, and we'll get you set up.
Count me in. The previous experience in Austi
I'd be concerned about merging a change to eventlet this late in the
cycle. Threading problems are notoriously difficult to find during
testing. I'd recommend pushing the patch to Gerrit, so that we can all try
it out when debugging, and we check it in after the Newton release.
Eric, +1 to your
Hi,
I would like to highlight this bug:
https://bugs.launchpad.net/tripleo/+bug/1619758
that will affect Keystone upgrade between Mitaka to Newton.
See my comment:
https://bugs.launchpad.net/tripleo/+bug/1619758/comments/1
Just to make sure people working on upgrades are aware about it :-)
Any
Neutrinos,
Because of holidays in US, it's probably safer to cancel the meeting for
the week starting Monday 5th.
Ask for your FFE, as needed on [1]
[1] https://review.openstack.org/#/c/360207/
Cheers,
Armando
__
OpenStack
Hello,
Recently, I noticed that on Ubuntu Xenial 'stud' for tls-proxy option
is no longer available and replaced by 'hitch'.
I filed a bug report and proposed a fix.
https://bugs.launchpad.net/devstack/+bug/1613071
https://review.openstack.org/#/c/355253/
Ian gave me +1, and could anyone else r
We're looking for a handful of community members to test our updated
OpenStack Summit mobile Apps. If you're interested, shoot me a note,
along with iOS/Android preference, and we'll get you set up.
Thank you,
Jimmy McArthur
Excerpts from Ken Giusti's message of 2016-09-02 11:05:51 -0400:
> On Thu, Sep 1, 2016 at 4:53 PM, Ian Wells wrote:
> > On 1 September 2016 at 06:52, Ken Giusti wrote:
> >>
> >> On Wed, Aug 31, 2016 at 3:30 PM, Ian Wells wrote:
> >
> >> > I have opinions about other patterns we could use, but I
Excerpts from Thierry Carrez's message of 2016-09-02 12:15:33 +0200:
> Sean Dague wrote:
> > Putting DB trigger failure analysis into the toolkit required to manage
> > an upgrade failure is a really high bar for new ops.
>
> I agree with Sean: increasing the variety of technologies used increases
release note just generate a bunch of html file. We can not use them for
track bug/issue.
For example, how to trace the backport/revert/re-open status for some
issue/feature if the reno notes is the only thing we have?
The reno is just a releasenote tool. It is not helpful for project
management.
If you really want some function like this, you may need this[0]
> Create named local volumes that persist in the location(s) you want!
[0] https://github.com/CWSpear/local-persist
On Sat, Sep 3, 2016 at 1:04 AM, Jeffrey Zhang
wrote:
>
> On Fri, Sep 2, 2016 at 11:48 PM, Paul Bourke
> wrote:
>
On Fri, Sep 2, 2016 at 11:48 PM, Paul Bourke wrote:
> In our Kilo based solution we were solving this using host bind mounts,
> e.g. -v /var/lib/nova:/var/lib/nova, where the directory on the left hand
> side can be mounted wherever you like. Two major issues with this approach
> are:
>
> 1) Koll
On Sep 2, 2016 08:44, "Brad Topol" wrote:
>
> Congratulations Ron!!! Very well deserved!!!
>
> --Brad
>
>
> Brad Topol, Ph.D.
> IBM Distinguished Engineer
> OpenStack
> (919) 543-0646
> Internet: bto...@us.ibm.com
> Assistant: Kendra Witherspoon (919) 254-0680
>
> Steve Martinelli ---09/01/2016 10
On Sep 2, 2016 09:39, "rezroo" wrote:
>
> Hello - I'm using Liberty release devstack for the below scenario. I have
created project "abcd" with "john" as Member. I've launched one instance, I
can use curl to list the instance. No problem.
>
> I then modify /etc/nova/policy.json and redefine "admin
On 08/15/2016 04:48 AM, Thierry Carrez wrote:
> Sean Dague wrote:
>> On 08/12/2016 01:10 PM, Walter A. Boring IV wrote:
>>> I believe there is a compromise that we could implement in Cinder that
>>> enables us to have a deprecation
>>> of unsupported drivers that aren't meeting the Cinder driver
>>
Hello - I'm using Liberty release devstack for the below scenario. I
have created project "abcd" with "john" as Member. I've launched one
instance, I can use curl to list the instance. No problem.
I then modify /etc/nova/policy.json and redefine "admin_or_owner" as
follows:
"admin_or_own
So this is hard problem to solve without native docker support (which
afaik it doesn't). One potential solution would be to write our own
"named volume" mechanism that will be configurable, after all it's
just bindmounted directory. However it will be hacky and costly to
maintain, although in reali
is the failure here something that comes up in gnocchi's test suite?
Could there be some way that oslo libraries run the test suites of all
consuming projects before a patch and/or a release? (apologies if we
already do this).
On 09/02/2016 12:17 PM, Matthew Thode wrote:
On 09/02/2016 03
On 09/02/2016 03:43 AM, Julien Danjou wrote:
> On Fri, Sep 02 2016, Julien Danjou wrote:
>
>> I'll look into fixing that, though any help would be welcome.
>
> My attempt at:
> https://review.openstack.org/364767
>
>
>
> ___
There are a few more details around critical fixes, libraries and their
releases based on critical fixes, stable branches, dates, etc. here
http://lists.openstack.org/pipermail/openstack-dev/2016-September/102829.html
On 9/2/16 12:03 PM, Nikhil Komawar wrote:
> Hi all,
>
>
> This is a email notic
On Thu, Aug 25, 2016 at 7:53 AM, Elizabeth K. Joseph
wrote:
> Hi everyone,
>
> On Friday, September 2nd from approximately 18:00 through 22:00 UTC
> Gerrit will be unavailable while complete project renames.
>
> Currently, we plan on renaming the following projects:
>
> openstack/smaug -> openstac
Hi all,
This is a email notice being sent to let all know that Newton 3 for
Glance has been released yesterday [1]. The RC-1 phase has begun and at
this time we are respecting all the freezes that are introduced as per
the release schedule [2].
Refresher (to those who are already familiar):
Focus
-
The feature freeze deadline was 1 Sept. All project teams should
be working on stabilization and last minute feature freeze exceptions.
General Notes
-
We are in the stabilization period before we prepare release
candidates during R-3.
All libraries are frozen and will o
Hi Kolla,
We have been experiencing a long running issue with Kolla that I have
brought up briefly a few times, but not made too much noise about.
I'm taking the time to write about it in the hopes that a) as a
community we may be able to solve it, and b) if other operators start
complaining
Congratulations Ron!!! Very well deserved!!!
--Brad
Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet: bto...@us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680
From: Steve Martinelli
To: "OpenStack Development Mailing List (not for usage questions)"
I agree with Jeffrey.
2016-09-02 11:52 GMT-03:00 Michał Jastrzębski :
> +1 to Jeffrey's points. We should deprecate old footer mechanism and
> remove it alltogether in Ocata timeframe.
>
> On 1 September 2016 at 23:51, Jeffrey Zhang
> wrote:
> > 1. so i think we need add the deprecated status to
On Fri, Sep 02 2016, Mike Bayer wrote:
> I've augmented it with mapper-level SQLAlchemy API use.
Awesome, thanks. :)
And "augmented" makes it sounds so futurist, whoohhh. :)
--
Julien Danjou
# Free Software hacker
# https://julien.danjou.info
signature.asc
Description: PGP signature
On Thu, Sep 1, 2016 at 4:53 PM, Ian Wells wrote:
> On 1 September 2016 at 06:52, Ken Giusti wrote:
>>
>> On Wed, Aug 31, 2016 at 3:30 PM, Ian Wells wrote:
>
>> > I have opinions about other patterns we could use, but I don't want to
>> > push
>>
>> > my solutions here, I want to see if this is r
+1 to Jeffrey's points. We should deprecate old footer mechanism and
remove it alltogether in Ocata timeframe.
On 1 September 2016 at 23:51, Jeffrey Zhang wrote:
> 1. so i think we need add the deprecated status to the include_footer option
> and print a warn.
> 2. when the use specifies both two
On 09/02/2016 04:43 AM, Julien Danjou wrote:
On Fri, Sep 02 2016, Julien Danjou wrote:
I'll look into fixing that, though any help would be welcome.
My attempt at:
https://review.openstack.org/364767
I've augmented it with mapper-level SQLAlchemy API use.
_
> We know:
>
> * It pretty much does what we intend it to do: allocations are added
> and deleted on server create and delete.
> * On manipulations like a resize the allocations are not updated
> immediately, there is a delay until the heal periodic job does its
> thing.
We know one more th
Thanks, Vladimir!
-Dmitry.
On Fri, Sep 2, 2016 at 4:22 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> Thanks for you efforts, FFE is granted, please go ahead. I hope we'll get
> it merged by 09/09/2016.
>
> Vladimir Kozhukalov
>
> On Fri, Sep 2, 2016 at 1:02 PM, Dmitry Klenov
> wr
Thanks for you efforts, FFE is granted, please go ahead. I hope we'll get
it merged by 09/09/2016.
Vladimir Kozhukalov
On Fri, Sep 2, 2016 at 1:02 PM, Dmitry Klenov wrote:
> Hi Fuelers,
>
> I would like to ask for a FFE for "Role Decomposition" feature. The spec
> is merged and can be fould at
Election details: https://governance.openstack.org/election/
Please read the stipulations and timelines for candidates and electorate
contained in this governance documentation.
Be aware, in the PTL elections if the program only has one candidate,
that candidate is acclaimed and there will be no
2016-09-02 12:45 GMT+02:00 Dirk Müller :
> Hi,
>
> I would like to suggest Javier Peña as an additional core reviewer for
> the packaging-rpm core group. He's been an extremely valueable
+1
Javier has done a good job as a reviewer, and is key contributor to
add RDO 3rd CI.
Good job!
H.
> con
+1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
For anyone interested in exercising the allocations stuff that Dan
added yesterday I wrote a little script that combines devstack and
gabbi to do a simple confirm of allocations being updated:
https://github.com/cdent/placement-exercise
The code that does all this is merged in master of nov
Hi,
I would like to suggest Javier Peña as an additional core reviewer for
the packaging-rpm core group. He's been an extremely valueable
contributor recently both doing regular reviews on the PRs as well as
contributing more to the packaging effort overall.
See http://stackalytics.com/?user_id=j
Sean Dague wrote:
> Putting DB trigger failure analysis into the toolkit required to manage
> an upgrade failure is a really high bar for new ops.
I agree with Sean: increasing the variety of technologies used increases
the system complexity, which in turn requires more skills to fully
understand
Hi Fuelers,
I would like to ask for a FFE for "Role Decomposition" feature. The spec is
merged and can be fould at [0]. We were unable to land the patch [1] to
Newton in time. So I would like to ask for extension till 09.09.2016 to
land this patch.
Changes made in the patch would introduce concep
After the discussion in the #openstack-tricircle channel, 3 candidates
available now, please vote the name for the new sub-project for api-gateway
functionality:
1. Triangel
The Triangel are dolls that bring luck
2. Tridonut
Three Donuts. Delicious food, often buy 3 get 1 free.
3. Trifen
Hi Aimee,
Thanks let us know.
I don't think it has a big impact to the current architecture and
user/dev. So it seems to be good to report it as a bug and target the
fix to N-release.
best regards,
Masahito
On 2016/09/02 10:10, Eric K wrote:
Hi Aimee,
Thanks for digging into it!
Here¹s m
Mike,
As per QoS spec [1], the behavior is:
``QoS policies could be applied:
- Per network: All the ports plugged on the network where the QoS policy
is
applied get the policy applied to them.
- Per port: The specific port gets the policy applied, when the port had
any
network
Minutes:
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-02-08.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-02-08.00.txt
Log:
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisyclou
Hi Michael.
When you update a network with a qos_policy_id it updates all ports on that
network too [1].
If you want to have a port on that network without any QoS features on it you
can make a policy with no rules attached.
This empty policy would override the networks QoS policy when it's attac
On Fri, Sep 02 2016, Julien Danjou wrote:
> I'll look into fixing that, though any help would be welcome.
My attempt at:
https://review.openstack.org/364767
--
Julien Danjou
;; Free Software hacker
;; https://julien.danjou.info
signature.asc
Description: PGP signature
__
Hi there,
So, fun fact, the latest _stable_ release of oslo.db entirely broke
Gnocchi. :-)
The culprit is the backport of "Correctly detect incomplete sort_keys
passed to paginate_query" at https://review.openstack.org/#/c/363827/
It turns out that while the backport might have been a good idea,
we are discussing the name in the #openstack-tricircle channel, if you are
interested in naming a new project, please join. After name is decided, we can
start to create regarding folder, launchpad, etc..., then divide Tricircle
project.
Best Regards
Chaoyi Huang(joehuang)
_
Hey all,
Quick question: If I have a network and a port, and neither has any QOS
policy set, and then I change the network to set the qos_policy_id,
should this new QOS policy affect traffic on the already-created port?
In other words, is this a network default for future ports (like with
p
Hey all,
Quick question: If I have a network and a port, and neither has any QOS
policy set, and then I change the network to set the qos_policy_id,
should this new QOS policy affect traffic on the already-created port?
In other words, is this a network default for future ports (like with
p
65 matches
Mail list logo
