Dugger, Donald D said on Mon, Aug 03, 2015 at 05:39:49AM +:
Also note that, although many capabilities can be represented by
simple key/value pairs (e.g. the presence of a specific special
instruction) that is not true for all capabilities (e.g. Numa topology
doesn't really fit into this
On Fri, Jul 3, 2015 at 9:11 AM, Duncan Thomas duncan.tho...@gmail.com wrote:
It was discussed on the mailing list, and at the weekly meeting. Mike had
had no response on the issue from the listed contact email, and the CI was
reporting failure for every patch for two months
On 3 Jul 2015
Morgan Fainberg wrote:
Lets step back away from tooz. Tooz for the sake of this conversation is as
much the same as saying zookeeper or consul or etcd, etc. We should be focused
(as both Flavio and Thierry said) on if we need DLM and what it will solve.
So IMHO part of the problem with just
On Mon, Aug 3, 2015 at 6:32 AM, Doug Hellmann d...@doughellmann.com wrote:
Do we have anyone willing to spend some time looking at the
incompatibilities Ned mentions below to ensure that we have a smooth
transition when 4.0 moves out of alpha?
Doug
Seems to work ok with keystone. There
+1.
From: Flavio Percoco [fla...@redhat.com]
Sent: Monday, August 03, 2015 12:30 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] A possible solution for HA
Active-Active
On 03/08/15 00:49
Clint Byrum wrote:
Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700:
On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote:
On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileorgegui...@redhat.com wrote:
I know we've all been looking at the HA Active-Active problem in
I'm usually for abstraction layers, but they don't always pay off very well due
to catering to the lowest common denominator.
Lets clearly define the problem space first. IFF the problem space can be fully
implemented using Tooz, then lets do that. Then the operator can choose. If
Tooz cant
On 7/30/15, 4:26 PM, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Steven Dake (stdake)'s message of 2015-07-30 15:27:15 +:
On 7/29/15, 1:23 PM, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Steven Dake (stdake)'s message of 2015-07-29 20:07:26
+:
Doug
Hi,
I'm planning to add a new ml2 driver and agent to neutron supporting
macvtap attachments [1]. Kyle already decided, that this code should
land in the neutron tree [2]. The normal approach till now was to copy
an existing agent code and modify accordingly, which lead to a lot of
duplicated
On Mon, Aug 3, 2015 at 8:41 AM Joshua Harlow harlo...@outlook.com wrote:
Clint Byrum wrote:
Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700:
On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote:
On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileorgegui...@redhat.com
Hi,
We had a very low turnout to the above meeting today. Hence, we did a
very short update and ended it. You may find more details here:
http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2015/glance_artifacts_sub_team.2015-08-03-14.10.html
--
Thanks,
Nikhil
Folks
As Sergii G. already pointed out if you want this solution to work in
production, you should provide common ways of synchronization between
different processing entities. Otherwise your very simple one-script
solution will be prone to errors such as race conditions and others. You
need to
On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
[...]
In order to make this work, it looks like we'd require:
* pbr changes so that it supports a mode where every commit on the
branch increments .Z
* infra changes to automatically push the corresponding tag when the
commit is
Thierry Carrez said on Mon, Aug 03, 2015 at 02:57:39PM +0200:
1. we can maintain a Changelog document directly in the source code.
Rather than being straightly backported from master, commits with
significant changes would be amended to additionally modify that document.
Wouldn't this cause a
Devananda van der Veen wrote:
On Mon, Aug 3, 2015 at 8:41 AM Joshua Harlow harlo...@outlook.com
mailto:harlo...@outlook.com wrote:
Clint Byrum wrote:
Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700:
On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez
If i understood correctly, the main difference is that the parse_rule
function is a private now in the oslo.policy library, also Jeffrey Zhang
has changed this function and put into nova.policy module. I offer remove
this function from the nova and make a public in the oslo.policy.
On Mon, Aug 3,
Jeremy Stanley wrote:
On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
[...]
In order to make this work, it looks like we'd require:
* pbr changes so that it supports a mode where every commit on the
branch increments .Z
* infra changes to automatically push the corresponding
Hi Elena, the tool looks very interesting.
Maybe try to spread out this proposal also through openstack-security@ ML.
BTW, I can't find the wrapper mentioned - am I missing something?
Regards,
Adam
On Mon, Aug 3, 2015 at 11:08 PM, Reshetova, Elena elena.reshet...@intel.com
wrote:
Hi,
We
hi all,
i am doing some work to change sahara to make greater use of
keystoneclient.session.Session objects and i am running into a strange
error when issuing the trusts.
the crux of this issue is that when i create Client objects by passing
all the parameters directly to the client, the
BTW, I did update the documentation a bit to cover recent questions [1]. Let me
know if I missed anything.
Thanks,
Ramy
[1]
https://github.com/rasselin/os-ext-testing/commit/0d8e4234c226273392391df3693292af43b1d2be
From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Monday, August 03,
On 08/04/2015 06:44 AM, Asselin, Ramy wrote:
Hi Tang,
Sorry the documentation on github is limited. I've been focusing on
getting an upstream solution working, and that's where it belongs and
should be maintained. I will take a quick look and add some tips as
discussed in this thread.
Of
I hacked up the LB agent and the OVS agent over some coffee - to see if
there are pieces that overlap. I believe there are - I'm hoping to
extract some code from each agent, into a common class. It's very WIP
but I'm hopeful that I'll be able to share some promising results soon.
Two weeks ago we had a discussion of where things stand in the collaboration
between Fuel and Puppet OpenStack projects [0].
[0] http://lists.openstack.org/pipermail/openstack-dev/2015-July/069925.html
Things that were good at that point:
- number of proposed patch sets
Things that needed
Hi Tang,
Sorry the documentation on github is limited. I’ve been focusing on getting an
upstream solution working, and that’s where it belongs and should be
maintained. I will take a quick look and add some tips as discussed in this
thread.
Of course if you have pull requests, I’m happy to
I see this as two tasks: 1) A refactoring to share common code and 2)
the addition of another agent following the pattern of the others.
I'd prefer that the two tasks not be mixed in the same review because
it makes it more difficult to review as I think Kevin eluded to. For
me, either could be
On Sat, Aug 1, 2015 at 8:03 PM, Boris Bobrov bbob...@mirantis.com wrote:
On Sat, Aug 1, 2015 at 3:41 PM, Clint Byrum cl...@fewbar.com wrote:
This too is overly complex and will cause failures. If you replace key 0,
you will stop validating tokens that were encrypted with the old key 0.
Hi Suro and Jay,
I checked discussion below, and I do believe we also need service-list(for
just magnum-api and magnum-conductor), but not so emergent requirement.
I also think service-list should not bind to k8s or swarm etc. (can use
coe-service etc.)
But I have more for below:
1) For k8s
On 03/08/15 19:48 +0200, Gorka Eguileor wrote:
On Mon, Aug 03, 2015 at 03:42:48PM +, Fox, Kevin M wrote:
I'm usually for abstraction layers, but they don't always pay off very well due
to catering to the lowest common denominator.
Lets clearly define the problem space first. IFF the
Hi Tang,
I thought I replied about this earlier. There seems to be a regression running
jobs directly on master, at least for newer versions of Jenkins. Running on a
slave does work.
Ramy
From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Monday, July 27, 2015 6:30 PM
To:
Thanks Jay/Kennan/Adrian for chiming in!
From this, I conclude that we have enough consensus to have 'magnum
service-list' and 'magnum coe-service-list' segregated. I will capture
extract of this discussion at the blueprint and start implementation of
the same.
Kennan,
I would request you
Hi Suro,
Yes, I did not see a strong reason for adding service-list to show all of
magnum system services, but it is nice to have.
But I did see a strong reason to rename service-list to
coe-service-list or others which might be more meaningful as I was often
asked by someone why does magnum
Hi Xiexs,
Definitely make sure you run nodepool commands as nodepool and not root:
sudo su - nodepool
Before starting nodepool on a fresh install, I usually manually build the image
first as it is easier to debug issues:
sudo su - nodepool
nodepool image-build image-name
Ramy
-Original
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Aug 3, 2015, at 6:09 PM, Flavio Percoco fla...@redhat.com wrote:
On 03/08/15 19:48 +0200, Gorka Eguileor wrote:
On Mon, Aug 03, 2015 at 03:42:48PM +, Fox, Kevin M wrote:
I'm usually for abstraction layers, but they don't always pay off very
Hi Ramy,
Cc Wienand,
Thanks to both of you and your suggestions help me solve this problem.
It was really a permission issue:
(debug info)
+sha256sum --check -
+grep: /opt/dib_cache/SHA256SUMS.ubuntu.trusty.amd64: Permission denied
Here grep command run as nodepool, but the file was owned by
I hope we can move this idea moving forward. I was disappointed to see
the spec abandoned.
Some of us from the large deployers group will be at the Ops Meetup. Will
there be any representation from Neutron there that we could discuss with
more?
Thanks,
Mike
On 8/3/15, 12:27 PM, Carl
Adrian,
If the reason to avoid leader election is because it is complicated and error
prone, this argument may not be true. Leader election is complicated in a pure
distributed system in which there is no centralized storage. However, Magnum
has a centralized database, so it is possible to
Hi Xiexs,
You are using disk image builder (DIB), so make sure your proxy is set
correctly also without the NODEPOOL_ prefix.
Those NODEPOOL_ prefixed variables are what would be used when DIB is not used
/ when the script approach is used with nova/glance (nodepool image-update). I
don’t
On 08/03/2015 10:07 PM, Rich Megginson wrote:
I'm running devstack in a VM (Fedora 21 host, EL 7.1.x VM) with a
static IP address (because dhcp was not working):
cat /etc/sysconfig/network-scripts/ifcfg-eth0 EOF
DEVICE=eth0
BOOTPROTO=static
DHCPCLASS=
HWADDR=$VM_MAC
IPADDR=192.168.122.5
Hi All,
When I ran “nodepool image-build image-name” to create a new image, I got
this error message:
…
INFO nodepool.image.build.dpc: + sudo -H virtualenv /usr/zuul-swift-logs-env
INFO nodepool.image.build.dpc: sudo: unable to resolve host fnst01
INFO nodepool.image.build.dpc: + sudo -H
Cool, Suro! It's great that we finally reach an agreement on this ;-)
2015-08-03 20:43 GMT-04:00 SURO suro.p...@gmail.com:
Thanks Jay/Kennan/Adrian for chiming in!
From this, I conclude that we have enough consensus to have 'magnum
service-list' and 'magnum coe-service-list' segregated. I
I'm running devstack in a VM (Fedora 21 host, EL 7.1.x VM) with a static
IP address (because dhcp was not working):
cat /etc/sysconfig/network-scripts/ifcfg-eth0 EOF
DEVICE=eth0
BOOTPROTO=static
DHCPCLASS=
HWADDR=$VM_MAC
IPADDR=192.168.122.5
NETMASK=255.255.255.0
GATEWAY=192.168.122.1
Perhaps the following can be used?
https://github.com/vaab/gitchangelog#gitchangelog
That does impose a commit message format, but then any kind of release
notes generated from a commit log will require some sort of standard to
be maintained (otherwise it's going to be tough to auto-generate
On Mon, Aug 3, 2015 at 5:47 PM, Steven Dake (stdake) std...@cisco.com
wrote:
On 7/30/15, 4:26 PM, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Steven Dake (stdake)'s message of 2015-07-30 15:27:15 +:
On 7/29/15, 1:23 PM, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Doug Hellmann's message of 2015-08-03 16:19:31 -0400:
Excerpts from Morgan Fainberg's message of 2015-08-04 06:05:56 +1000:
On Aug 4, 2015, at 05:49, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Sergey Vilgelm's message of 2015-08-03 22:11:50 +0300:
On
Will hold another meeting tomorrow. If you have items for the agenda,
please update the Wiki.
Regards,
Paul Michali (pc_m)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 03/08/15 08:32 -0700, Joshua Harlow wrote:
Morgan Fainberg wrote:
Lets step back away from tooz. Tooz for the sake of this conversation is as
much the same as saying zookeeper or consul or etcd, etc. We should be focused
(as both Flavio and Thierry said) on if we need DLM and what it will
Hi folks, we are discussing operations on sensitive data.
May I ask you what security controls Pacemaker provides?
How we could audit its operations and data it is accessing?
The same question arises when discussing native Keystone solution.
From the security perspective, reduction of attack
Hi,
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Mon, Aug 3, 2015 at 12:44 PM, Adam Heczko ahec...@mirantis.com wrote:
Hi folks, we are discussing operations on sensitive data.
May I ask you what security controls Pacemaker provides?
Pacemaker doesn't exchange any
Hi,
In the PoC, the status synchronization is done by the proxy node running with
periodic task to poll the recent changed status, for example, VM status, volume
status, and port status, etc. One proxy node will be responsible for one
cascaded OpenStack instance, and configured with one user
On Mon, Aug 03, 2015 at 12:28:27AM -0700, Clint Byrum wrote:
Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700:
On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote:
On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileor gegui...@redhat.com
wrote:
I know we've all
Excerpts from Davanum Srinivas (dims)'s message of 2015-08-02 21:16:32 -0400:
Sean, Nova-cores,
The following Nova review is stuck:
https://review.openstack.org/#/c/198065/
What's the minimum features in oslo.policy that we have to add in
oslo.policy to unblock that work?
If we get
Doug,
All the features needed for Nova to work is present in oslo.policy
(i.e. all features from old oslo-incubator copy is present in
oslo.policy)
-- dims
On Mon, Aug 3, 2015 at 5:16 AM, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Davanum Srinivas (dims)'s message of 2015-08-02
Agree that we use polling mode to synchronize resource status, but it's a
bit weird to deploy a localized service for just polling. Maybe we can
define a status synchronizatioin task to handle such work so it can be done
by cascade service itself. If multiple cascade service is deployed, to
avoid
On 03/08/15 00:49 +0200, Gorka Eguileor wrote:
On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote:
On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileor gegui...@redhat.com wrote:
I know we've all been looking at the HA Active-Active problem in Cinder
and trying our best to figure out
Lets step back away from tooz. Tooz for the sake of this conversation is as
much the same as saying zookeeper or consul or etcd, etc. We should be focused
(as both Flavio and Thierry said) on if we need DLM and what it will solve.
Once we have all of that defined, the use of an abstraction such
Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700:
On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote:
On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileor gegui...@redhat.com
wrote:
I know we've all been looking at the HA Active-Active problem in Cinder
and
On Fri, Jul 31, 2015 at 03:18:39PM -0700, Clint Byrum wrote:
Excerpts from Mike Perez's message of 2015-07-31 10:40:04 -0700:
On Fri, Jul 31, 2015 at 8:56 AM, Joshua Harlow harlo...@outlook.com wrote:
...random thought here, skip as needed... in all honesty orchestration
solutions like
Hi Matt,
Thanks for your reply.
You mean to say what needs to be used for the scheduling ( CPUS, RAM,
Storage etc ) has to be put into the Nova DB by implementing the APIs in
every Nova compute server?
These implementations acts as a nova-agents ?
-Pradeep
On 31 July 2015 at 18:03, Matt
On Fri, Jul 31, 2015 at 12:47:34PM -0700, Joshua Harlow wrote:
Joshua Harlow wrote:
Mike Perez wrote:
On Fri, Jul 31, 2015 at 8:56 AM, Joshua Harlowharlo...@outlook.com
wrote:
...random thought here, skip as needed... in all honesty orchestration
solutions like mesos
Flavio Percoco wrote:
[...]
So, to summarize, I love the effort behind this. But, as others have
mentioned, I'd like us to take a step back, run this accross teams and
come up with an opinonated solution that would work for everyone.
Starting this discussion now would allow us to prepare
On Mon, Aug 03, 2015 at 10:22:42AM +0200, Thierry Carrez wrote:
Flavio Percoco wrote:
[...]
So, to summarize, I love the effort behind this. But, as others have
mentioned, I'd like us to take a step back, run this accross teams and
come up with an opinonated solution that would work for
On Mon, Aug 03 2015, Thierry Carrez wrote:
The last thing we want is to rush a solution that would only solve a
particular project use case. Personally I'd like us to pick the simplest
solution that can solve most of the use cases. Each of the solutions
bring something to the table --
This has been implemented. Thanks all for participation.
On 8/3/15 10:14 AM, Nikhil Komawar wrote:
We asked Stuart personally during the recent Glance mid-cycle if he
wanted to join and he said yes. Guess it's appropriate time for
rotation now.
On 8/1/15 11:44 PM, Flavio Percoco wrote:
On
For now, take this code and merge with exiting horizon setup
(openstack_dashbord) and restart horizon. With that you will see
loadbalancers_v2 panel on the left pane.
Thanks,
Vivek
From: santosh sharma chitr.praya...@gmail.commailto:chitr.praya...@gmail.com
Reply-To: OpenStack Development
On 7/30/2015 1:02 AM, Li, Xiaoyan wrote:
Hi all,
I created an encryption type, and create a volume in Ceph with the volume type.
cinder encryption-type-create
But failed to attach it to a VM. The error message shows that no device_path in
connection_info.
^[[01;31m2015-07-30 05:55:57.117
Excerpts from Devananda van der Veen's message of 2015-08-03 08:53:21 -0700:
On Mon, Aug 3, 2015 at 8:41 AM Joshua Harlow harlo...@outlook.com wrote:
Clint Byrum wrote:
Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700:
On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike
FUCK OFF
From: dava...@gmail.commailto:dava...@gmail.com
dava...@gmail.commailto:dava...@gmail.com
Reply-To:
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, August 3, 2015 at
Hello,
I would like to request feature freeze exception for the
implementation of Nested Quota Driver for Nova, which does the quota
management of nested projects.
Blueprint
https://blueprints.launchpad.net/nova/+spec/nested-quota-driver-api
Excerpts from Sergey Vilgelm's message of 2015-08-03 19:05:52 +0300:
If i understood correctly, the main difference is that the parse_rule
function is a private now in the oslo.policy library, also Jeffrey Zhang
has changed this function and put into nova.policy module. I offer remove
this
On 4 August 2015 at 06:06, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Thierry Carrez's message of 2015-08-03 18:11:53 +0200:
Jeremy Stanley wrote:
On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
[...]
In order to make this work, it looks like we'd require:
*
On 4 August 2015 at 02:46, Alexis Lee alex...@hp.com wrote:
Thierry Carrez said on Mon, Aug 03, 2015 at 02:57:39PM +0200:
1. we can maintain a Changelog document directly in the source code.
Rather than being straightly backported from master, commits with
significant changes would be amended
On Mon, Aug 3, 2015 at 9:37 PM, Doug Hellmann d...@doughellmann.com wrote:
Making that function public may be the most expedient fix, but the
parser was made private for a reason, so before we expose it we
should understand why, and if there are alternatives (such as
creating a fixture in
Jay makes a good point here. The service-list output is specific to the
“service” abstraction in the COE, not the system services that are part of
magnum. The suggested rename from service-list to coe-service-list would make
this distinction more clear.
Adrian
On Jul 30, 2015, at 2:40 AM, Jay
Kevin, sorry for the delay in response. Keeping up on this thread was
getting difficult while on vacation.
tl;dr: I think it is worth it to talk through the idea of inserting
some sort of a subnet group thing in the model to which floating ips
(and router external gateways) will associate. It
On 2015-08-03 16:42:06 + (+), Ian Cordasco wrote:
Auto-tagging seems to be the least amount of work. That could be
done as a post-commit hook or post-receive (depending on where we
implement it) upstream.
Well, not as a git hook but we would likely run it as a CI job in
zuul's post
Hi, Justin,
Perhaps you meant to click through to
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce
and unsubscribe? Let me know if you need help figuring that interface
out.
Doug
Excerpts from Justin Hammond's message of 2015-08-03 18:00:02 +:
FUCK OFF
From:
On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote:
Hi everyone,
A month ago the stable branch team decided to move away from
synchronized stable point releases and enable continuous stable branch
delivery instead.
The end goal is that every commit on a stable branch for a service
Hi Suro and others, comments on this? Thanks.
2015-07-30 5:40 GMT-04:00 Jay Lau jay.lau@gmail.com:
Hi Suro,
In my understanding, even other CoE might have service/pod/rc concepts in
future, we may still want to distinguish the magnum service-list with
magnum coe-service-list.
On 8/3/15, 11:11, Thierry Carrez thie...@openstack.org wrote:
Jeremy Stanley wrote:
On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
[...]
In order to make this work, it looks like we'd require:
* pbr changes so that it supports a mode where every commit on the
branch
Hi Graham,
Can we have your GSLB pull request merged to the repo
https://github.com/gslb/gslb-specs/pull/1/files
https://github.com/gslb/gslb-specs/pull/1/files ? I would like to send
another pull request based on these changes.
Regards
Kunal
On Jun 30, 2015, at 8:38 AM, Hayes, Graham
On Mon, Aug 03, 2015 at 07:01:45PM +1000, Morgan Fainberg wrote:
Lets step back away from tooz. Tooz for the sake of this conversation is as
much the same as saying zookeeper or consul or etcd, etc. We should be
focused (as both Flavio and Thierry said) on if we need DLM and what it will
We'll have a chance to discuss DB mutual exclusion at the API nodes at the
Cider mid-cyle, which starts tomorrow.
The details, issues, and realistic schedule for that will be a key piece to
this whole puzzle, since anything else is seen as a temporary solution.
-Original Message-
From:
For example, to parallel the conversation with databases:
We want a database. Well, that means mongodb, postgres, mysql, berkeleydb,
etc
Oh, well, I need it to be a relational db, Well, that means postgresq, mysql,
etc
Oh, and I need recursive queries... that excludes even more.
We
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday August 4th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone
On Aug 2, 2015, at 7:40 PM, 王华
wanghua.hum...@gmail.commailto:wanghua.hum...@gmail.com wrote:
Hi all,
As discussed in the Vancouver Summit, we are going to drop the bay lock
implementation. Instead, each conductor will call Heat concurrently and rely on
heat for concurrency control.
On Mon, Aug 03, 2015 at 03:42:48PM +, Fox, Kevin M wrote:
I'm usually for abstraction layers, but they don't always pay off very well
due to catering to the lowest common denominator.
Lets clearly define the problem space first. IFF the problem space can be
fully implemented using
Hi folks,
the Kolla community is pleased to announce the release of the Kolla Liberty 2
milestone. This release fixes 77 bugs and implements 18 blueprints!
Our community developed the following notable features:
* Source building of containers
* Ansible Deployment for core services
* High
Thanks to all of those who attended the midcycle. We had more than 20
attendees this cycle and excellent participation -- also some new faces!
My apologies for the Google Hangouts failure. We ended up switching to
Webex for the audio/video conferencing and it scaled significantly
better. I
I would just de-dup anything that is obvious into a common class to inherit
from. Don't go through any major re-factorings because that will just take
longer to review and will probably need to be reworked anyway when we spend
more time on the modular agent stuff later in the cycle.
On Mon, Aug
Excerpts from Thierry Carrez's message of 2015-08-03 18:11:53 +0200:
Jeremy Stanley wrote:
On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote:
[...]
In order to make this work, it looks like we'd require:
* pbr changes so that it supports a mode where every commit on the
On Aug 3, 2015, at 21:14, Davanum Srinivas dava...@gmail.com wrote:
agree. Native HA solution was already ruled out in several email
threads by keystone cores already (if i remember right). This is a
devops issue and should be handled as such was the feedback.
Correct. This is generally
Oleg, thanks for the provided information. As discussed verbally, most
core reviewers are now busy with fixing critical bugs, so you might get
delayed responses. Keeping in mind, let's target Wednesday, Aug 5 as the
last deadline. With that said, let's minimize review iterations so core
Eugene,
To increase focus and ensure velocity increase, we decided to descope the
following patch from the current release cycle [1]. This willl have minor
effect on supported use cases, but will allow us to focus on the required
parts [2] [3].
[1] https://review.openstack.org/#/c/203537/
[2]
Hi Vivek,
How to get the lbaas v2 UI up with mentioned changelist?
Thanks
Santosh
On Wed, Jul 29, 2015 at 8:24 AM, Jain, Vivek vivekj...@ebay.com wrote:
Initial code for horizon lbaas v2 dashboard submitted:
https://review.openstack.org/#/c/206797
Thanks,
vivek
From: Jain, Vivek
agree. Native HA solution was already ruled out in several email
threads by keystone cores already (if i remember right). This is a
devops issue and should be handled as such was the feedback.
Thanks,
-- dims
On Mon, Aug 3, 2015 at 7:03 AM, Sergii Golovatiuk
sgolovat...@mirantis.com wrote:
Hi,
Excerpts from Davanum Srinivas (dims)'s message of 2015-08-03 06:46:26 -0400:
Doug,
All the features needed for Nova to work is present in oslo.policy
(i.e. all features from old oslo-incubator copy is present in
oslo.policy)
Great! I was worried that the copy local to nova had somehow been
Fine, then this simple bash based solution proposed by Boris [1] LGTM and
is not over thinked.
Maybe add kind of md5 or sha1 checksum functionality to confirm if keys
were rotated correctly and are in sync.
[1] http://paste.openstack.org/show/406674/
Regards,
Adam
On Mon, Aug 3, 2015 at 2:03
Hi everyone,
A month ago the stable branch team decided to move away from
synchronized stable point releases and enable continuous stable branch
delivery instead.
The end goal is that every commit on a stable branch for a service
project will get a .Z version increment, and a tag be pushed to
On Mon, Aug 3, 2015 at 7:14 AM, Davanum Srinivas dava...@gmail.com wrote:
agree. Native HA solution was already ruled out in several email
threads by keystone cores already (if i remember right). This is a
devops issue and should be handled as such was the feedback.
I'm sure you are right.
Do we have anyone willing to spend some time looking at the
incompatibilities Ned mentions below to ensure that we have a smooth
transition when 4.0 moves out of alpha?
Doug
--- Begin forwarded message from Ned Batchelder ---
From: Ned Batchelder n...@nedbatchelder.com
To: testing-in-python
1 - 100 of 123 matches
Mail list logo
