Hi,
> Are there any effort on OpenStack packaging?
The short answer is yes. We are putting efforts to migrate all
our packaging activities to the community RPM/DEB projects.
Long story is as follows:
At the moment Fuel is distributed as a set of RPM packages. This
Packaging CI that Aleksandra m
Looks like it was unanimously decision :)
Oleksii, my congratulations !
Good work. I will add you to necessary groups ;)
On 17 March 2016 at 04:34, Huangtianhua wrote:
> +1 ：）
>
> -邮件原件-
> 发件人: Sergey Kraynev [mailto:skray...@mirantis.com]
> 发送时间: 2016年3月16日 18:58
> 收件人: OpenStack Develop
Here are some of my raw points,
1. For the driver mentioned, I think we not necessary use bay-driver here,
as have network-driver, volume-driver, maybe it is not needed to introduce
driver in bay level.(bay is higher level than network or volume)
maybe like
coes/
swarm/
mesos/
kubernet
All,
Does anyone have experience deploying Magnum in a highly-available fashion? If
so, I'm interested in learning from your experience. My biggest unknown is the
Conductor service. Any insight you can provide is greatly appreciated.
Regards,
Daneyon Hansen
_
Hi everyone!
I’m looking for boilerplates/good practices regarding to testing
extensions with core code.
Since we unlocked Nailgun extensions system [0] and now there
is a possibility to install the extensions from external sources we
want to also provide a way to test your own extensions against
Guys,
Fuel has own implementation of pacemaker [1]. It's functionality may be
useful in other projects.
[1] https://github.com/fuel-infra/puppet-pacemaker
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Sat, Feb 13, 2016 at 6:20 AM, Emilien Macchi
wrote:
>
> On Feb 12, 2016
Sylvain Bauza identified an issue with reno not properly handling
release notes that had been deleted (such as when a change is
reverted). The new release of reno, 1.6.1, should resolve that.
Existing release notes will be rebuilt and republished when a new
patch lands or when projects are tagged,
I built an IRC bot
https://anticdent.org/purple-irc-bot.html
that provides (see the blog posting):
* granular logging
* some in channel commands to get recent history and recent mentions
of your nick
* inter channel transclusion of messages
and put it on a few channels (openstack-sdks,
Hi everyone,
I'd like to announce my candidacy for the RPM Packaging for OpenStack PTL. I
am putting up the candidacy because I would feel honored to continue doing the
PTL role, but I'm also fine with passing on the torch. At the end of the
day what matters is that the project becomes successful
On 14 March 2016 at 11:08, Thomas Goirand wrote:
>
> From a distribution package maintainer perspective, the most annoying
> part is that there's no easy way to get the web app use the JS libs from
> the OS, and there's no system wide registry of installed components.
>
There's a basic difference
After reviewing your logs[1], it seems that quotas are not working
correctly in your plugin. There are no statements about tenants being
marked dirty, etc.
I think you are missing the quota registry setup code in your plugin init.
Here is the ML2 example:
https://github.com/openstack/neutron/blob/
On 2016-03-19 05:10:18 -0500 (-0500), Monty Taylor wrote:
[...]
> It would also be good to tie off with the security team about
> this. One of the reasons we stopped publishing debs years ago is
> that it made us a de-facto derivative distro. People were using
> our packages in production, includin
What are the various reasons which block you to work on bug reports?
This question goes especially to the new contributors but also to the
rest of us. For me, personally, it's that most bug reports miss the
steps to reproduce which allow me to see the issue on my local system
before I start to di
Hongbin,
I think Adrian makes some excellent points regarding the adoption of
Barbican. As the PTL for Barbican, it's frustrating to me to constantly
hear from other projects that securing their sensitive data is a
requirement but then turn around and say that deploying Barbican is a
problem.
I
Hi,
I noticed that expand/migrate/contract was revert in
https://review.openstack.org/#/c/239922/
There is a new CMD 'online_data_migrations' was introduced to Nova and some
data-migration scripts have been added.
So I wonder will Nova keep expand the DB schema at beginning of live upgrade
like
Hello Friends,
We are now going into the Newton cycle of Searchlight and I would be honored
if you’ll allow me to continue serving in the PTL role.
Searchlight has come a long way in the Mitaka cycle and it is certainly due
to some passionate work from a small, but expanding team of contributors.
We're almost to the finish line with Mitaka!
Focus
-
Project teams following the cycle-with-milestone model should be
testing their release candidates and fixing release-critical bugs.
Project teams following the cycle-with-intermediary model should
ensure they have at least one Mitaka relea
Hi Shinobu,
There are some differences between clouds, the major task of jacket is how to
shield the differences. So that jacket will not be an API gateway, it has the
objects management and function processing, for example :
1. Unified resource uuid allocation: When users call jacket resource
Forgive me for the top post and also for asking the obvious (with my
Operator hat on)
Relying on an external service for certificate store - is the best
option - assuming of course that the certificate store is actually also
highly available.
Is that the case today with Barbican?
According to th
+1 Here's another not counting vote and cheer!
--Rocky
+1 for Tony! (my vote does not count, but still wanted to cheer!)
-- Dims
On Fri, Mar 18, 2016 at 4:38 PM, Anita Kuno wrote:
> On 03/18/2016 04:11 PM, Matt Riedemann wrote:
>> I'd like to propose tonyb for stable-maint-core. Tony is
It's good that there are concerns about the stability of the current
auth process.
But...
- there are many tests (unit and functional) show that current
functionality was not broken.
- there are new unit tests specially for sig v4 functionality
- i try to commit this patch in current development/t
FFE extension granted until March 18 for:
https://review.openstack.org/#/c/286495/
On Wed, Mar 16, 2016 at 10:46:41PM +0300, Dmitry Klenov wrote:
> Folks,
>
> Majority of the commits for HugePages feature are merged in time [0].
>
> One commit for validation is still to be merged [1]. So we woul
I'm actively working on release notes this week, and plan to prepare
our repos for Mitaka release end of this week and early next week.
Please do not merge new features, and if you need exceptions please
reply to this email or ping me on IRC.
We don't want to break our CI just before the release :-
Thank you for your explanation in detail.
On Thu, Mar 17, 2016 at 12:57 PM, zs wrote:
> Hi Shinobu,
>
> There are some differences between clouds, the major task of jacket is how
> to shield the differences. So that jacket will not be an API gateway, it has
> the objects management and function p
Hello everyone,
Designate's release candidate for the end of the Mitaka cycle is
available!
You can find the RC1 source code tarball at:
https://tarballs.openstack.org/designate/designate-2.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this RC
Hey Vitaly,
Thanks for your feedback, it's an important notice. However, I think
you didn't get the problem quite well so let me explain it again.
You see, Nailgun unit tests are failing due to races or deadlocks
happened by two transactions: test transaction and fake thread
transaction, and we m
On 14/03/16 16:38, Dan Prince wrote:
> http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt
>
> Our top reviewer over the last half a year ejuaso (goes by Ozz for
> Osorio or jaosorior on IRC). His reviews seem consistent, he
> consistently attends the meetings and he chimes in on lo
John Garbutt wrote on 03/08/2016 03:36:30 PM:
> From: John Garbutt
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 03/08/2016 03:37 PM
> Subject: Re: [openstack-dev] [nova] Identifying Mitaka release blockers
>
> On 3 March 2016 at 13:10, Markus Zoeller wrote:
Hello, everyone.
I have config a web server (tengine) as a proxy server for swift, and sent a
GET request via a chrome browser in order to access swift container. From the
log file, it can be seen that web server has pass the request to swift, but
swift returns an unauthorized error. Log file r
2016-03-17 3:22 GMT-07:00 Jordan Pittier :
>>
>> If wanting to add negative tests, it is a nice option to implement
>> these tests on each component repo with Tempest plugin interface. We
>> can avoid operating negative tests on different component gates and
>> each component team can decide what n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everyone,
It is with great pleasure that I announce that I will be the PTL again for
Newton, which will be my third release for openstack-manuals. I'm overwhelmed
by the positive messages I've received since announcing my candidacy, and very
e
On 03/18/2016 01:16 PM, Boris Pavlovic wrote:
> Hi everybody,
>
> What about if we just create new project for alternative Gerrit WebUI and
> use it?
> I don't think that with current set of web frameworks it would be too hard.
>
> Best regards,
> Boris Pavlovic
It's called vinz: http://git.open
Le 18/03/2016 09:48, Dulko, Michal a écrit :
On Fri, 2016-03-18 at 08:27 +, Tan, Lin wrote:
Hi,
I noticed that expand/migrate/contract was revert in
https://review.openstack.org/#/c/239922/
There is a new CMD 'online_data_migrations' was introduced to Nova and some
data-migration script
On 03/14/2016 03:38 PM, Dan Prince wrote:
http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt
Our top reviewer over the last half a year ejuaso (goes by Ozz for
Osorio or jaosorior on IRC). His reviews seem consistent, he
consistently attends the meetings and he chimes in on lots
Hi dashboard plugins team
(sahara-dashboard, trove-dashboard, magnum-ui, murano-dashboard)
As Horizon i18n liaison, I would like to have a consensus on a rough schedule
of translation import for Horizon plugins.
Several plugins and horizon itself already released RC1.
For Horizon translation, we
On 16 March 2016 at 20:15, Thierry Carrez wrote:
> Hello everyone,
>
> Heat and Neutron just produced a release candidate for the end of the Mitaka
> cycle! You can find their RC1 source code tarballs at:
Heat team also plan to cut RC2 on the week.
>
> https://tarballs.openstack.org/heat/heat-6.
On 2016-03-19 02:28:48 + (+), Amrith Kumar wrote:
> Maybe we could collaborate and build something that'd work for
> multiple projects? Happy to help with this. It is clearly a
> problem that some projects seem to be facing and there aren't any
> good solutions there.
Rossella Sblendido wa
On Thu, Mar 17 2016, Thomas Goirand wrote:
> We don't have enough of such actions, and we have a way too many
> dependencies, with many duplicate functionalities too. Just to name a few:
> - oslo.concurrency vs lockfile
You made me check, but this is not true anymore. Lockfile is not used
anywher
> On Mar 18, 2016, at 8:31 AM, Cory Benfield wrote:
>
>>
>> On 18 Mar 2016, at 13:57, Brian Haley wrote:
>>
>> On 03/17/2016 06:04 PM, Doug Wiegley wrote:
> Here is the non comprehensive list of usages based on what trees I
> happen to have checked out (which is quite a few, but not a
Dear All Neutron Developers and Reviewers,
I have a query/concern related to the parsing of options in
python-neutronclient.
I would like to bring this up, as it "may" also impact the transition of
the CLIs to the openstack client as well.
NeutronClient is pretty special in its behavior, and has
On Mar 14, 2016 11:32 AM, "Sean McGinnis" wrote:
> On Mon, Mar 14, 2016 at 10:37:52AM -0400, Sean Dague wrote:
> > On 03/14/2016 10:24 AM, Ian Cordasco wrote:
> > >
> > >
> > > -Original Message-
> > > From: Davanum Srinivas
> > > Reply: OpenStack Development Mailing List (not for usage
Hello everyone,
Nova is next to produce a release candidate for the end of the Mitaka
cycle! Congratulations to all the Nova devs. You can find the RC1 source
code tarball at:
https://tarballs.openstack.org/nova/nova-13.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a
I would like to announce my candidacy for PTL for the Kolla team for the Newton
release cycle.
I have been heavily involved with Kolla since the Liberty cycle. A few of my
major technical contributions include:
* Bringing Ansible to Kolla
* Containerized host dependencies (kolla-toolbox)
* Na
2016-03-17 15:05 GMT-07:00 Rochelle Grober :
> (Sorry for the top post. It was this or bottom post because of company
> choice of email systems)
(no problem :)
> Integration tests, corner cases, negative tests. Lots of names that don't
> have clear definitions in this discussion. But, it seems
Filed it at https://bugs.launchpad.net/taskflow/+bug/1559496
Thanks,
Kanthi
On Sat, Mar 19, 2016 at 9:30 PM, Joshua Harlow
wrote:
> Interesting error, that could be a bug and perhaps we should ensure
> upgrade is more thread-safe (with a lock on upgrade); can u open a bug @
> bugs.launchpad.net
Josh,
Haha, see note from russellb :)
http://git.openstack.org/cgit/openstack/nova/tree/nova/network/rpcapi.py#n308
On Thu, Mar 17, 2016 at 6:44 PM, Joshua Harlow wrote:
> In a follow-up to this.
>
> Seems like the patch to disable/disallow this itself found some 'violations'
> @
> http://logs.o
On 03/18/2016 12:22 PM, Doug Hellmann wrote:
We need the warning to show up in the calling side, so if we can look
at the name there and emit the warning that would be a good start. Then
changing oslo.messaging to not allow calling private methods would be an
API break, and require raising the ma
Hi all!
I want to start this thread because I'm tired. I spent a lot of time, but I
can't review as easy as it was with old interface. New Gerrit is awful.
Here are several issues:
* It is not possible to review patches at mobile phone. "New" "modern"
theme is not adopted for small screens.
* Lea
Interesting error, that could be a bug and perhaps we should ensure
upgrade is more thread-safe (with a lock on upgrade); can u open a bug @
bugs.launchpad.net/taskflow for that and we can try to add said lock
(that should hopefully resolve what u are seeing, although if it doesn't
then the bug
Hi Joshua,
Thanks for all your inputs.
We are using this feature successfully. But I rarely see an issue related
to concurrency.
To give you a brief, we use eventlets and every job runs in a separate
eventlet thread.
In the job execution part, we use taskflow functionality and persist all
the de
I thought that a big part of the use case with Magnum + Barbican was
Certificate management for Bays?
-Rob
From: "Dave McCowan (dmccowan)"
Reply-To: OpenStack List
Date: Saturday, 19 March 2016 14:56
To: OpenStack List
Subject: Re: [openstack-dev] [magnum] High Availability
The most basic requ
Hi KevinI read the wiki and quite liked it. Good going. I would like to contribute to it once the work starts Do let me know about it.ThanksJanki
On 16/03/2016 4:03 AM, zs wrote:
> Hi all,
>
> There is a new project "jacket" to manage multiply clouds. The jacket
> wiki is: https://wiki.openstack.org/wiki/Jacket
> Please review it and give your comments. Thanks.
>
> Best Regards,
>
> Kevin (Sen Zhang)
>
>
i don't know exact details of ei
Hi All-
I've decided that I will not be running for Astara PTL this coming cycle.
It's been great helping the project grow and find its place within the
OpenStack tent over the last 8 months or so. We're a small group of
developers and I think its important to stir the pot and let another
contrib
Hi Erno,From my perspective, your value is priceless. You clarified
fundamental concepts to us.
Consistently over time, after interacting with you, we walked away with deeper
understanding, fresh, improved perspectives and with better confidence.
It's a great value have a Person like you
On 03/16/2016 11:01 PM, Ken'ichi Ohmichi wrote:
2016-03-16 19:29 GMT-07:00 Adam Young :
On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote:
Hi
I have one proposal[1] related to negative tests in Tempest, and
hoping opinions before doing that.
Now Tempest contains negative tests and sometimes patc
On 2016-03-18 08:53:11 +0530 (+0530), Armando M. wrote:
> It's be nice if Neutron didn't overlap as much with Nova, Ironic, QA and
> infra sessions, but I appreciate this could be a tall order.
It seems like every project wants to avoid overlap with Infra
sessions, so I'm not sure it will be easy
On Mar 17, 2016, at 9:41, Markus Zoeller wrote:
> What are the various reasons which block you to work on bug reports?
The number one reason for me is lack of information. The main things I want to
know are, what version, what commands/API calls did you do, what was the
behavior, what behavior
Thanks Graham, I was going to use the dashboard creator and this is a good
solution. Will see how I can enable something like this for Trove.
-amrith
P.S. Will you be in Austin?
> -Original Message-
> From: Hayes, Graham [mailto:graham.ha...@hpe.com]
> Sent: Friday, March 18, 2016 10:37
Hi Janki,
I am very glad you like it. I will mail you when the work starts. :)
Best Regards,
Kevin (Sen Zhang)
At 2016-03-16 21:20:52, "Janki Chhatbar" wrote:
Hi Kevin
I read the wiki and quite liked it. Good going. I would like to contribute to
it once the work starts
Do let me kno
Hello everyone,
Horizon's release candidate for the end of the Mitaka cycle is
available!
You can find the RC1 source code tarball at:
https://tarballs.openstack.org/horizon/horizon-9.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this RC1 will
There are two types of quotas you may want to enforce in an OpenStack project:
technical and business.
Technical quotas are things that are hard limits of the system based on either
actual resources available or protecting the system itself. For example, you
can't provision a 2TB volume if you
Hi all,
Just like we did in Kilo, Newton will have a blocker migration at the
front that ensures things we expect to be migrated online in Mitaka have
completed. That needs to land first, so please do not approve any DB
migrations until this lands:
https://review.openstack.org/#/c/289450/
I'll
Specs are proposed to the 'approved' subdirectory and when they are
completely implemented in launchpad (the blueprint status is
'Implemented'), we should move the spec from the 'approved' subdirectory
to the 'implemented' subdirectory in the nova-specs repo.
For example:
https://review.opens
Hi Jerico,
Internal db storage for job binaries was added at
the start of EDP as an alternative for sites that do
not have swift running. Since then, we've also added
integration with manila so that job binaries can be
stored in manila shares.
You are correct, storing lots of binaries in the
Hello.
I'm the author of fuel-infra/puppet-pacemaker and I guess I would be able
to merge the code from "fuel-infra/puppet-pacemaker" to
"openstack/puppet-pacemaker"
We will be having a single set of pcmk_* types and two providers for the
each type: "pcs" and "xml", there is also a "noop" provider
The most basic requirement here for Magnum is that it needs a safe place to
store credentials. A safe place can not be provided by just a library or even
by just a daemon. Secure storage is provided by either hardware solution (an
HSM) or a software solution (SoftHSM, DogTag, IPA, IdM). A pr
Hi neutrinos,
A kind reminder for next week's meeting. More on the agenda [1].
Cheers,
Armando
[1] https://wiki.openstack.org/wiki/Network/Meetings
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi Shinobu,
Thanks for your questions. My reply is behind your questions. :)
Best Regards,
Kevin (Sen Zhang)
At 2016-03-17 12:43:14, "Shinobu Kinjo" wrote:
>Thank you for your explanation in detail.
>
>On Thu, Mar 17, 2016 at 12:57 PM, zs wrote:
>> Hi Shinobu,
>>
>> There are some differences
Hello everyone,
Cinder is the next project team to produce a release candidate for the
end of the Mitaka cycle! You can find the RC1 source code tarball at:
https://tarballs.openstack.org/cinder/cinder-8.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a release
candidat
On Fri, Mar 18, 2016, at 10:31 AM, Andrey Kurilin wrote:
> Hi all!
> I want to start this thread because I'm tired. I spent a lot of time, but I
> can't review as easy as it was with old interface. New Gerrit is awful. Here
> are several issues:
>
> * It is not possible to review patches at
I am submitting myself as a candidate as Cue PTL for the Newton cycle.
I have been involved in the Cue project since its inception and would like
to help continue its development to make it a production ready message
broker provisioning/management service.
Some things I’d like to work on for Newt
Emilien,
Agree on the rant. But not clear on concrete proposal to fix it.
Spend more time "fixing" CI and use Tempest as a gate is a bit wage.
Unless we test known working version of each project in TripleO CI you are
dependent on health of other components.
Thanks,
Arkady
-Original Message--
Hello everyone,
Heat and Neutron just produced a release candidate for the end of the
Mitaka cycle! You can find their RC1 source code tarballs at:
https://tarballs.openstack.org/heat/heat-6.0.0.0rc1.tar.gz
https://tarballs.openstack.org/neutron/neutron-8.0.0.0rc1.tar.gz
https://tarballs.open
On 03/16/2016 05:22 AM, Julien Danjou wrote:
On Wed, Mar 16 2016, Attila Fazekas wrote:
The quota usage handling MUST happen in the same DB transaction as the
resource record (volume, server..) create/update/delete .
[…]
We have a transaction capable DB, to help us,
not using it would be l
On 03/16/2016 10:02 AM, Csaba Henk wrote:
Hi,
I'm asking for a Feature Free Exception for the update_access code for
Ganesha library and the two GlusterFS drivers (glusterfs, glusterfs-native).
This benefits the whole project in terms of getting closer to the point
when the backward compatiblit
After conferring with aovchinnikov about the remaining bugs against the
LXD driver, I have decided that it's better for Manila if we remove the
driver from the tree before the Mitaka release.
The goal of adding the driver was to create a new, faster, first party
Manila driver which had proper
On 14 March 2016 at 14:26, Dan Prince wrote:
> Looking at the stats for the last 180 days I'd like to propose we
> cleanup TripleO core a bit:
>
> http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt
>
> There are a few reviewers with low numbers of reviews (just added to
> the trip
On 17/03/16 18:29, "Sean Dague" wrote:
>On 03/17/2016 11:57 AM, Markus Zoeller wrote:
>
>> Suggested action items:
>>
>> 1. I close the open wish list items older than 6 months (=138 reports)
>>and explain in the closing comment that they are outdated and the
>>ML should be used for f
Hi.
We're running a Magnum pilot service - which means it's being
maintained just like all other OpenStack services and running on the
production infrastructure, but only available to a subset of tenants
for a start.
We're learning a lot in the process and will happily report on this in
the next
On 16 March 2016 at 22:45, Thierry Carrez wrote:
> Hello everyone,
>
> Heat and Neutron just produced a release candidate for the end of the
> Mitaka cycle! You can find their RC1 source code tarballs at:
>
> https://tarballs.openstack.org/heat/heat-6.0.0.0rc1.tar.gz
>
> https://tarballs.openstac
As we were working through reviews for the Mitaka release, the Trove team was
trying to track groups of reviews that were needed for a specific milestone,
like m-1, or m-3 or in the recent days for rc1.
The only way we could find was to have someone (in this instance, me) 'star'
the reviews tha
On 18/03/2016 14:19, Amrith Kumar wrote:
> As we were working through reviews for the Mitaka release, the Trove
> team was trying to track groups of reviews that were needed for a
> specific milestone, like m-1, or m-3 or in the recent days for rc1.
>
> The only way we could find was to have someon
Thomas Goirand wrote:
On 03/14/2016 03:28 PM, Davanum Srinivas wrote:
Ian,
+1 to get rid of that dependency if possible.
+1 for any action aiming toward removing *any* dependency.
We don't have enough of such actions, and we have a way too many
dependencies, with many duplicate functionaliti
On 03/19/2016 01:43 AM, Tony Breeds wrote:
> On Sun, Mar 13, 2016 at 12:15:23PM +, Amrith Kumar wrote:
>> Hi,
>>
>> Sorry for the blast mail, this is targeted at the stable-maint team. The
>> following five changes are now ready to merge. Two of them are changes
>> proposed by the bot and three
On 03/18/2016 04:11 PM, Matt Riedemann wrote:
> I'd like to propose tonyb for stable-maint-core. Tony is pretty much my
> day to day guy on stable, he's generally in every stable team meeting
> (which is not attended well so I appreciate it), and he's as proactive
> as ever on staying on top of gat
Hello everyone,
Senlin is the latest milestone-based project to produce a release
candidate for the end of the Mitaka cycle! You can find the RC1
source code tarball at:
https://tarballs.openstack.org/senlin/senlin-1.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a release
From: GHANSHYAM MANN
Subject: Re: [openstack-dev] [QA][all] Propose to remove negative tests from
Tempest
Date: Fri, 18 Mar 2016 10:05:39 +0900
> On Fri, Mar 18, 2016 at 9:06 AM, Ken'ichi Ohmichi
> wrote:
>> 2016-03-17 4:05 GMT-07:00 Andrea Frittoli :
>>> On Thu, Mar 17, 2016 at 2:57 AM Ken'ic
On 03/16/2016 09:34 AM, gordon chung wrote:
>
>
> On 16/03/2016 7:10 AM, Attila Fazekas wrote:
>>
>> NO : For any kind of extra quota service.
>>
>> In other places I saw other reasons for a quota service or similar,
>> the actual cost of this approach is higher than most people would think so
On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
> Hi
>
> I have one proposal[1] related to negative tests in Tempest, and
> hoping opinions before doing that.
>
> Now Tempest contains negative tests and sometimes patches are being
> posted for adding more negative tests, but I'd
On Mon, 14 Mar 2016, Chris Dent wrote:
wsgi-intercept (I maintain that) can use httplib2, http.lib or
requests (and if you go back a few versions even more) so those tests
could be updated to use requests and still use wsgi-intercept if that
was desired.
I've just released a version of wsgi-in
On 3/17/16 1:53 AM, Linpeimin wrote:
Hello, everyone.
I have config a web server (tengine) as a proxy server for swift, and
sent a GET request via a chrome browser in order to access swift
container. From the log file, it can be seen that web server has pass
the request to swift, but swift retur
In a follow-up to this.
Seems like the patch to disable/disallow this itself found some
'violations' @
http://logs.openstack.org/24/289624/3/check/gate-oslo.messaging-src-dsvm-full-amqp1-centos7/e3b485c/console.html.gz#_2016-03-11_00_06_56_177
Details: {u'message': u'Unable to associate float
How to run tests in /tricircle/test/functional *... .
When I try to run individual tests as python test_pod.py it shows error
Traceback (most recent call last):
File "test_pod.py", line 22, in
from tricircle.api import app
ImportError: No module named tricircle.api
I even tried to run tests
On Fri, Mar 18, 2016 at 8:36 AM, reedip banerjee wrote:
> Dear All Neutron Developers and Reviewers,
>
> I have a query/concern related to the parsing of options in
> python-neutronclient.
> I would like to bring this up, as it "may" also impact the transition of
> the CLIs to the openstack clien
Hi all!
This is a heads up for you that we've found an issue [1] in IPA that
changes the behavior for those of you with several hard drives. The
difference is in the way our ramdisks pick the root device for
deployment, when no root device hints [2] are provided. Namely:
- The old ramdisk pick
Steve,
Congratulations on the release!!!
Regards,
Daneyon
On Mar 17, 2016, at 9:32 AM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
The Kolla community is pleased to announce the release of Mitaka
milestone RC1. This may look like a large list of features, but really
it was finish
All - Thanks for reviewing the 100' view Sahara slide in yesterday's team
meeting. I made the updates we discussed and have posted the updated (and
hopefully final) slide for you to check here:
https://docs.google.com/presentation/d/1-iGE2LJRs7X5KXABuWOzbekQbQI0JT27QTK7A_RGZkw/edit?usp=sharing
Hi Gordon,
Thank you for your suggestion.
I think jacket is different from tricircle. Because tricircle focuses on
OpenStack deployment across multiple sites, but jacket focuses on how to manage
the different clouds just like one cloud. There are some differences:
1. Account management and API
A quick reminder that we are in the last hours for PTL candidate announcements.
If you want to stand for PTL, don't delay, follow the instructions on the
wikipage and make sure we know your intentions:
https://wiki.openstack.org/wiki/PTL_Elections_March_2016
Make sure your candidacy have been sub
101 - 200 of 327 matches
Mail list logo
