Hi, Keystone guys,
Could we have a talk about DB2 CI enablement on this Monday, 8PM central US
time? which is Tuesday 9AM beijeing time?
For your questions, here are my answers:
1) Is the team going to be responsive to requests unlike last time there
was a problem?
(yanfengxi) Yes, problems
On 06/11/2015 06:29 AM, Sean Dague wrote:
On 06/09/2015 06:42 PM, Jeremy Stanley wrote:
As discussed in the Liberty Design Summit Moving apps to Python 3
cross-project workshop, the way forward in the near future is to
switch to the pure-python PyMySQL library as a default.
Joe,
When looking at stackalytics [2] for each project, we don't see any
noticeably change in number of reviews, contributors, or number of commits
from before and after each project joined OpenStack.
I can't agree on this.
*) Rally is facing core-reviewers bottleneck currently.
We have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Not on the list either, but I want to +1 what Henry said. Yamamoto's
reviews expand to the whole code base and are pretty always *very* usefu
l.
On 06/12/2015 11:39 PM, Henry Gessau wrote:
Although I am not on your list I would like to add my +1!
Hi all,
I have created the blueprint about the default configuration file. I think we
should add the essential configuration like datastore_manager in default
trove.conf.
The blueprint is here
https://blueprints.launchpad.net/trove/+spec/default-configuration-items
Any suggestion about
On Sun, Jun 14, 2015 at 10:46 PM, Thomas Goirand z...@debian.org wrote:
On 06/11/2015 11:31 PM, Nikhil Manchanda wrote:
Hi Thomas:
I just checked and I don't see suds as a requirement for trove.
I don't think it should be a requirement for the trove debian package,
either.
Thanks,
-Original Message-
From: Joshua Harlow [mailto:harlo...@outlook.com]
Sent: Friday, June 12, 2015 5:49 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [taskflow] Returning information from reverted
flow
Dulko, Michal wrote:
Hi,
One of the stated problems the 'big tent' is supposed to solve is:
'The binary nature of the integrated release results in projects outside
the integrated release failing to get the recognition they deserve.
Non-official projects are second- or third-class citizens which can't get
development
Hi,
The email mail below was a little cryptic so here is the general plan to
move forwards:
1. Oslo.vmware:- rebase and update the patch
https://review.openstack.org/#/c/114503. This will sort out the issues
that we have with the exception hierarchy
2. Nova: hopefully manage to get reviews for
On 12 June 2015 at 05:39, Dolph Mathews dolph.math...@gmail.com wrote:
On Thu, Jun 11, 2015 at 12:34 AM, Robert Collins robe...@robertcollins.net
wrote:
On 11 June 2015 at 17:16, Robert Collins robe...@robertcollins.net
wrote:
This test conflates setup and execution. Better like my
On 06/15/2015 07:30 AM, Boris Pavlovic wrote:
Joe,
When looking at stackalytics [2] for each project, we don't see any
noticeably change in number of reviews, contributors, or number of
commits from before and after each project joined OpenStack.
I can't agree on this.
*) Rally
On 06/12/2015 07:58 AM, Bogdan Dobrelya wrote:
I'm actually happy to hear from you, since we were discussing together
about that over the last 2 summits, without real plan between both groups.
I believe as a first steep, the contribution policy to Fuel library
should be clear and *prevent
+1
On Mon, Jun 15, 2015 at 12:16 PM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Not on the list either, but I want to +1 what Henry said. Yamamoto's
reviews expand to the whole code base and are pretty always *very* usefu
l.
On 06/12/2015
+1
On Mon, Jun 15, 2015 at 12:14 PM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
No doubt +1.
On 06/12/2015 09:44 PM, Kevin Benton wrote:
Hello!
As the Lieutenant of the built-in control plane[1], I would like
Rossella Sblendido to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/13/2015 04:38 PM, Jeff Feng wrote:
*I'm using OVSHybridIptablesFirewallDriver in
ovs_neutron_plugin.ini* / [securitygroup] firewall_driver =
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
enable_security_group =
+1 to the plan garyk, vipin et.al
-- dims
On Mon, Jun 15, 2015 at 7:00 AM, Gary Kotton gkot...@vmware.com wrote:
Hi,
The email mail below was a little cryptic so here is the general plan to
move forwards:
1. Oslo.vmware:- rebase and update the patch
https://review.openstack.org/#/c/114503.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
No doubt +1.
On 06/12/2015 09:44 PM, Kevin Benton wrote:
Hello!
As the Lieutenant of the built-in control plane[1], I would like
Rossella Sblendido to be a member of the control plane core
reviewer team.
Her review stats are in line with
On 06/15/2015 06:20 AM, Joe Gordon wrote:
One of the stated problems the 'big tent' is supposed to solve is:
'The binary nature of the integrated release results in projects outside
the integrated release failing to get the recognition they deserve.
Non-official projects are second- or
Hello!
I’ve never had to set datastore_manager in trove.conf and I can launch Trove
just fine with either one of three setup methods, devstack, redstack, or
following the detailed installation steps provided in the documentation.
My suspicion is that the steps you are using to register your
+1 Great job with Cinder.
-Ryan
- Original Message -
From: Steven Dake (stdake) std...@cisco.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Sunday, June 14, 2015 1:48:48 PM
Subject: [openstack-dev] [kolla] Proposal for new
I agree with Amrith – we should try to understand what the problem first.
The datastore_manager config setting is passed down to the guest in the
guest_info.conf file along with a few other config settings that the guest
uses. I believe the intention is that trove_guestagent.conf is passed down
Hi Kyle,
-Original Message-
From: Kyle Mestery [mailto:mest...@mestery.com]
Sent: June 15, 2015 04:26
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] VLAN-aware VMs meeting
On Fri, Jun 12, 2015 at 8:51 AM, Ildikó Váncsa
Thomas,
Is anyone willing to the work needed to get the existing Nova vmware
driver scenarios with any alternate python library acceptable to
Debian? If not, this discussion is moot.
-- dims
On Mon, Jun 15, 2015 at 9:16 AM, Thomas Goirand z...@debian.org wrote:
On 06/15/2015 11:31 AM, Joe
On 15 June 2015 at 08:03, 郑振宇 zheng.zhe...@outlook.com wrote:
Hi All,
When querying instance actions using API: nova instance-action-list, nova
will response with a table show in below:
root@controller:~# nova instance-action-list
fcbba82f-60a1-4785-84f2-88bcf2da7e7e
Thanks for your reply @amrith.
The datastore_manager refer to the manager you gonna use, mysql or others. If
you don't set it, the default value is None. And if it's None, guest agent will
fail to start up.
That's why I think it's the necessary configuration we need to focus on. I
don't
Good day, fellow fuelers
Fuel API is a powerful tool that allow for very fine tuning of deployment
settings and parameters, and we all know that UI exposes only a fraction of
the full range of attributes client can pass to Fuel installer.
However, there are very little documentation that
On Mon, Jun 15, 2015 at 5:00 AM, Feng Xi BJ Yan yanfen...@cn.ibm.com
wrote:
Hi, Keystone guys,
Could we have a talk about DB2 CI enablement on this Monday, 8PM central
US time? which is Tuesday 9AM beijeing time?
Works for me, I'll make a note to be in the channel at 8 PM central.
Thanks
This weekend, I discussed the requested change at length with Mike. I think
before moving forward, we need a better understanding of what is trying to be
achieved.
Request: Add the ability to verify migrations are completed prior to contract.
As discussed here previously, I worked out a setup
I think there is some desire to see more documentation around here as there
are some odd interactions with parts of the data payload, and perhaps
documenting these may improve some of them.
I think the gaps in order of most used are:
* node object create / update
* environment networks ( the fact
On Mon, Jun 15, 2015 at 4:16 PM, Thomas Goirand z...@debian.org wrote:
On 06/15/2015 11:31 AM, Joe Gordon wrote:
Nova itself doesn't depend on suds anymore.
A quick grep still shows references to suds (that's in Kilo, but the
master branch shows similar results):
Your git repo is out of
On Mon, Jun 15, 2015 at 7:40 AM, Ildikó Váncsa ildiko.van...@ericsson.com
wrote:
Hi Kyle,
-Original Message-
From: Kyle Mestery [mailto:mest...@mestery.com]
Sent: June 15, 2015 04:26
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev]
On Mon, Jun 15, 2015 at 6:30 AM, Sean Dague s...@dague.net wrote:
On 06/11/2015 06:29 AM, Sean Dague wrote:
On 06/09/2015 06:42 PM, Jeremy Stanley wrote:
As discussed in the Liberty Design Summit Moving apps to Python 3
cross-project workshop, the way forward in the near future is to
On 15/06/15 19:20 +0900, Joe Gordon wrote:
One of the stated problems the 'big tent' is supposed to solve is:
'The binary nature of the integrated release results in projects outside the
integrated release failing to get the recognition they deserve. Non-official
projects are second- or
Hi All,
I am trying to create a Volume for VMFS with a Volume Type (selected Volume
Type selected has extra_specs).I am receiving an error Volume creation
failed incase if the volume-type has extra-specs.
Cinder doesn't support Volume creation if the volume-type has extra-specs? Is
this
On 15.06.2015 13:59, Bogdan Dobrelya wrote:
I believe as a first steep, the contribution policy to Fuel library
Sorry, the step, it is not so steep.
should be clear and *prevent new forks of upstream modules* to be
accepted in future. This will prevent the technical dept and fork
maintain
On 06/15/2015 11:31 AM, Joe Gordon wrote:
Nova itself doesn't depend on suds anymore.
A quick grep still shows references to suds (that's in Kilo, but the
master branch shows similar results):
etc/nova/logging_sample.conf:qualname = suds
nova/tests/unit/test_hacking.py: def
Well, I suggest continuing
https://review.openstack.org/#/c/179051/
It basically requires to update docstrings of handler functions
according to [1]. This way the documentation is as close to the code as
possible.
With some work one could add automatic generation of docs out of
JSONSchema
We are happy to announce the release of:
mox3 0.8.0: Mock object framework for Python
This release is part of the liberty release series.
With source available at:
http://git.openstack.org/cgit/openstack/mox3
For more details, please see the git log history below and:
It would be great to see the DB2 CI tests for Keystone. Can we see results
of a pass first? Before enabling the CI?
Thanks,
Steve Martinelli
OpenStack Keystone Core
From: Feng Xi BJ Yan yanfen...@cn.ibm.com
To: openstack-dev@lists.openstack.org
Cc: Dan Moravec mora...@us.ibm.com
Hi Adrian,
The new app resource that is being implemented
(https://review.openstack.org/#/c/185147/)
does not enforce name uniqueness.
This issue was discussed here sometime back.
Earlier thread:
http://lists.openstack.org/pipermail/openstack-dev/2015-March/058858.html
The main argument
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi All
On 27/05/15 09:14, Thomas Goirand wrote:
tl;dr: - We'd like to push distribution packaging of OpenStack on
upstream gerrit with reviews. - The intention is to better share
the workload, and improve the overall QA for packaging *and*
Hi,
The value is sent down from Task Manager based on a value that is setup as part
of the datastore.
It is actually a bad thing if you set a value of the datastore_manager in the
taskmanager.conf file on the Trove controller, and attempt to launch some other
datastore.
The way this works is
Planning on weekly meetings for a while, since this are several things to
discuss. See the agenda on the wiki page:
https://wiki.openstack.org/wiki/Meetings/VPNaaS
There are a bunch of questions to discuss.
See you Tuesday!
If your asking the cloud provider to go through the effort to install Magnum,
its not that much extra effort to install Barbican at the same time. Making it
a dependency isn't too bad then IMHO.
Thanks,
Kevin
From: Adrian Otto [adrian.o...@rackspace.com]
Sent:
On 06/08/2015 01:55 PM, Kuvaja, Erno wrote:
One thing I like about plan D
is that it would give also indicator how much the stable branch has moved in
each individual project.
The only indication you will get is how many patches it has. I fail to
see how this is valuable information. No info
Hi Kyle,
Thanks for your support. Let's go for the meeting channel option then, so the
final details for the tomorrow's meeting are:
Time: Tuesday (06. 16.), 17:00UTC - 18:00UTC
Location: #openstack-meeting-4
I will add a pointer to the agenda, when we have it!
Best Regards,
Ildikó
On 06/10/2015 03:46 PM, Thierry Carrez wrote:
The main issue with B is that it doesn't work well once server component
versions start to diverge, which will be the case starting with Liberty.
Review that policy then.
We already couldn't (with Swift using separate versioning), but we worked
Yes, the log deletion should be optional.
The question is what should be the default behavior. Should the default be to
delete the logs and provide a flag to keep them, or keep the logs by default
and provide a override flag to delete them?
Delete-by-default is consistent with the view that
On 06/10/2015 11:27 AM, Dave Walker wrote:
On 10 June 2015 at 09:53, Thomas Goirand z...@debian.org wrote:
On 06/05/2015 02:46 PM, Thierry Carrez wrote:
So.. summarizing the various options again:
Plan A
Just drop stable point releases.
(-) No more release notes
(-) Lack of reference
We are thrilled to announce the release of:
python-openstackclient 1.4.0: OpenStack Command-line Client
This release is part of the liberty release series.
With source available at:
https://git.openstack.org/cgit/openstack/python-openstackclient
For more details, please see the git log
Tim,
On Jun 9, 2015, at 10:04 AM, Tim Hinrichs t...@styra.com wrote:
Hi Joe,
The telco slides are powerpoint, but are hosted on google drive ...
Thanks very much for the OpEx slides (and corresponding design doc)!
Is there a deck link for Congress: Introduction, Status, and Future Plans
Hi Joe,
Here's the link to the Intro to Congress slide deck.
https://docs.google.com/file/d/0ByDz-eYOtswScTlmamlhLXpmTXc/edit
While I'm at it, here are the instructions for the Congress Hands On Lab.
https://docs.google.com/document/u/1/d/1lXmMkUhiSZYK45POd5ungPjVR--Fs_wJHeQ6bXWwP44/pub
All
On 6/15/15, 09:24, Thomas Goirand z...@debian.org wrote:
On 06/08/2015 01:55 PM, Kuvaja, Erno wrote:
One thing I like about plan D
is that it would give also indicator how much the stable branch has
moved in
each individual project.
The only indication you will get is how many patches it has.
Hi Sahara Team,
Just notice that the CloudBreak (https://github.com/sequenceiq/cloudbreak)
also support running on top of OpenStack, can anyone show me some
difference between Sahara and CloudBreak when both of them using OpenStack
as Infrastructure Manager?
--
Thanks,
Jay Lau (Guangya Liu)
On Jun 15, 2015, at 11:06 AM, Tim Hinrichs t...@styra.com wrote:
Hi Joe,
Here's the link to the Intro to Congress slide deck.
Thank you! I should have re-checked the wiki. :)
jd
__
OpenStack Development Mailing List
Please see https://review.openstack.org/#/c/186617 - Nova Instance Users and
review.
We're working hard on trying to get heat - nova - instance - barbican secret
storage workflow working smoothly.
Also related are: https://review.openstack.org/#/c/190404/ - Barbican ACL's and
On 6/15/15 9:21 AM, Philip Schwartz wrote:
This weekend, I discussed the requested change at length with Mike. I
think before moving forward, we need a better understanding of what is
trying to be achieved.
Request: Add the ability to verify migrations are completed prior to
contract.
As
Adrian,
On Tue, Jun 16, 2015 at 2:39 AM, Adrian Otto adrian.o...@rackspace.com
wrote:
Madhuri,
On Jun 15, 2015, at 12:47 AM, Madhuri Rai madhuri.ra...@gmail.com
wrote:
Hi,
Thanks Adrian for the quick response. Please find my response inline.
On Mon, Jun 15, 2015 at 3:09 PM, Adrian
Hi, John
Thanks for your reply, I will follow your instructions.
It will be great if I can help out with any part of the plan, I'm really happy
to do it.
BR,
Zheng
Date: Mon, 15 Jun 2015 14:50:41 +0100
From: j...@johngarbutt.com
To: openstack-dev@lists.openstack.org
Subject: Re:
Hi Adrian,
If I summarize your option, it would be,
1) Have a function like this,
magnum bay-create --name swarmbay --baymodel swarmbaymodel
--baymodel-property-override apiserver_port=8766
And then magnum pass that property to override baymodel default properties,
and create the bay.
2)
On 06/15/2015 08:45 PM, Madhuri wrote:
+1 Kevin. We will make Barbican a dependency to make it the default
option to secure keys.
Regards,
Madhuri
On Tue, Jun 16, 2015 at 12:48 AM, Fox, Kevin M kevin@pnnl.gov
mailto:kevin@pnnl.gov wrote:
If your asking the cloud provider to go
Regardless of what the API defaults to, could we have the CLI prompt/warn so
that the user easily knows that both options exist? Is there a precedent
within OpenStack for a similar situation?
E.g.
solum app delete MyApp
Do you want to also delete your logs? (default is Yes):
JSCS in Horizon has been extended with the John Papa style guidelines to
enforce consistent angularjs code style*. It's no longer just a findbug
tool. I don't have time to investigate - can ESLint perform the same role
for Horizon?
Current Horizon activity involves a whole lot of bringing code
I think app names should be unique per tenant. My opinion is that this should
be solums default behavior and does not require an extra setting in the config
file.
I feel the pain of non unique names when I play with my own vagrant environment
and deploy multiple 'test' apps. To identify the
Hi all,
We don’t have a rough draft API doc yet, so I’m suggesting that we postpone
tomorrow morning’s meeting until next week. Does anyone have any other agenda
items, or want the meeting tomorrow?
Thanks,
doug
On Jun 2, 2015, at 10:52 AM, Doug Wiegley doug...@parksidesoftware.com
wrote:
+1 Kevin. We will make Barbican a dependency to make it the default option
to secure keys.
Regards,
Madhuri
On Tue, Jun 16, 2015 at 12:48 AM, Fox, Kevin M kevin@pnnl.gov wrote:
If your asking the cloud provider to go through the effort to install
Magnum, its not that much extra effort to
Awesome, glad to see it's proposed.
On 16/06/15 11:41, Nikhil Komawar wrote:
Hi,
As per the discussion during the last weekly Glance meeting (14:51:42at
http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-11-14.00.log.html
), we will begin a short drivers' meeting where anyone
+1,
I just have one question. Do we want to able resume for WF in error state?
I mean isn't real resume it should be more of a rerun, don't you think?
So in an error state we will create new executor and just re run it
Thanks Limor
-Original Message-
From: Lingxian Kong
Excerpts from Fox, Kevin M's message of 2015-06-15 15:59:18 -0700:
No, I was confused by your statement:
When we create a bay, we have an ssh keypair that we use to inject the ssh
public key onto the nova instances we create.
It sounded like you were using that keypair to inject a public
Thanks Winson for the write-up, very detailed infomation. (the format was good)
I'm totally in favor of your idea, actually, I really think you
proposal is complementary to my proposal in
https://etherpad.openstack.org/p/vancouver-2015-design-summit-mistral,
please see 'Workflow
On 16 June 2015 at 16:21, Richard Jones r1chardj0...@gmail.com wrote:
JSCS in Horizon has been extended with the John Papa style guidelines to
enforce consistent angularjs code style*. It's no longer just a findbug
tool. I don't have time to investigate - can ESLint perform the same role
for
Sorry, wrong patch. That one added the style requirement to the project
contribution guidelines. This is the one that added the .jscsrc config:
https://review.openstack.org/#/c/185725/
On Tue, 16 Jun 2015 at 14:21 Richard Jones r1chardj0...@gmail.com wrote:
JSCS in Horizon has been extended
On 06/15/2015 01:16 PM, Dmitry Tantsur wrote:
On 06/15/2015 07:07 PM, Jay Pipes wrote:
It has come to my attention in [1] that the microversion spec for Nova
[2] and Ironic [3] have used the project name -- i.e. Nova and Ironic --
instead of the name of the API -- i.e. OpenStack Compute and
Cristina Aiftimiei wrote:
The puppetlabs-openstack clearly states:
Limitations
* High availability and SSL-enabled endpoints are not provided by this
module.
As Matt touched on, you really should be building your own 'composition
layer' for deploying production services
On 15 June 2015 at 13:07, Jay Pipes jaypi...@gmail.com wrote:
It has come to my attention in [1] that the microversion spec for Nova [2]
and Ironic [3] have used the project name -- i.e. Nova and Ironic --
instead of the name of the API -- i.e. OpenStack Compute and OpenStack
Bare Metal -- in
Bug ticket for python-magnumclient gate test:
https://bugs.launchpad.net/python-magnumclient/+bug/1465375
On Jun 15, 2015, at 11:07 AM, Tom Cammann
tom.camm...@hp.commailto:tom.camm...@hp.com wrote:
Review up for making it voting: https://review.openstack.org/#/c/191921/
It would probably be a
On 06/15/2015 04:55 PM, James Page wrote:
Hi All
On 27/05/15 09:14, Thomas Goirand wrote:
tl;dr: - We'd like to push distribution packaging of OpenStack on
upstream gerrit with reviews. - The intention is to better share
the workload, and improve the overall QA for packaging *and*
On 06/15/2015 11:48 AM, Thomas Goirand wrote:
On 06/15/2015 04:55 PM, James Page wrote:
The problem of managing delta and allowing a good level of
distribution independence is still going to continue to exist and will
be more difficult to manage due to the tighter coupling of development
My main issue with having the user generate the keys/certs for the kube
nodes
is that the keys have to be insecurely moved onto the kube nodes.
Barbican can
talk to heat but heat must still copy them across to the nodes, exposing the
keys on the wire. Perhaps there are ways of moving secrets
On 6/12/15, 3:55 PM, Clint Byrum cl...@fewbar.com wrote:
I think you missed it is not tested in the gate as a root cause for
some of the ambiguity. Anecdotes and bug reports are super important for
knowing where to invest next, but a test suite would at least establish a
base line and
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
(as of Mon, 15 Jun 15:00 UTC, diff since 1 Jun)
Open: 159 (+9)
5 new (0), 51 in progress (+6), 0 critical, 12 high (+2) and 12 incomplete
Review up for making it voting: https://review.openstack.org/#/c/191921/
It would probably be a good plan to run the functional tests on the
python-magnumclient,
although I'm not too sure how to set that up.
Tom
On 15/06/15 18:47, Adrian Otto wrote:
Tom,
Yes, let’s make it voting now. I
Tom,
On Jun 15, 2015, at 10:59 AM, Tom Cammann tom.camm...@hp.com wrote:
My main issue with having the user generate the keys/certs for the kube nodes
is that the keys have to be insecurely moved onto the kube nodes. Barbican can
talk to heat but heat must still copy them across to the
3. Build the controls into our process with a way of storing the
current release cycle information to only allow contract’s to
occur at a set major release and maintain the column in the model
till it is ready to be removed major release + 1 since the
migration was added.
2015-06-15 19:50 GMT+02:00 Clint Byrum cl...@fewbar.com:
Excerpts from Jay Pipes's message of 2015-06-15 10:07:39 -0700:
It has come to my attention in [1] that the microversion spec for Nova
[2] and Ironic [3] have used the project name -- i.e. Nova and Ironic --
instead of the name of
On Mon, 15 Jun 2015, Clint Byrum wrote:
I'm a little bit worried that we don't have a guiding principle to point
at somewhere. Perhaps the API WG can encode guidance either way (We use
project names, or we use service types).
I think it's a good idea to encode the principle, whatever it is,
Excerpts from Doug Hellmann's message of 2015-06-09 16:08:16 -0400:
Excerpts from Doug Hellmann's message of 2015-06-09 13:25:26 -0400:
Until now we have encouraged project teams to prepare their own
library releases as new versions of projects were needed. We've
started running into a
I¹d like to propose Michael McCune for CoreSec membership.
I¹ve worked with Michael (elmiko) on numerous security tasks and
bugs, and he has a great grasp on security concepts and is very active
in the OpenStack security community. I think he would be a natural
choice for CoreSec.
smime.p7s
Joe Gordon wrote:
[...]
Below is a list of the first few few projects to join OpenStack after
the big tent, All of which have now been part of OpenStack for at least
two months.[1]
* Mangum - Tue Mar 24 20:17:36 2015
* Murano - Tue Mar 24 20:48:25 2015
* Congress - Tue Mar 31 20:24:04
+1 for non-Barbican support first, unfortunately Barbican is not very well
adopted in existing installation.
Madhuri, also please keep in mind we should come with solution which should
work with Swarm and Mesos as well in further.
—
Egor
From: Madhuri Rai
Hello,
I haven't seen any false positives in a few weeks from the functional
tests, but I have seen a couple reviewers missing the -1 from the
non-voting job
when there has been a legitimate failures.
I think now would be a good time to turn 'check-functional-dsvm-magnum' to
voting.
Thanks,
On 06/15/2015 07:07 PM, Jay Pipes wrote:
It has come to my attention in [1] that the microversion spec for Nova
[2] and Ironic [3] have used the project name -- i.e. Nova and Ironic --
instead of the name of the API -- i.e. OpenStack Compute and
OpenStack Bare Metal -- in the HTTP header that a
+1 from me Tom.
On Mon, Jun 15, 2015 at 1:15 PM, Tom Cammann tom.camm...@hp.com wrote:
Hello,
I haven't seen any false positives in a few weeks from the functional
tests, but I have seen a couple reviewers missing the -1 from the non-voting
job
when there has been a legitimate failures.
I
On Sun, Jun 14, 2015 at 05:48:48PM +, Steven Dake (stdake) wrote:
I am proposing Harm Waites for the Kolla core team.
+1!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Tom,
Yes, let’s make it voting now. I went through the full review queue over the
weekend, and I did find a few examples of functional tests timing out after 2
hours. It did not look to me like they actually ran, suggesting a malfunction
in the setup of the test nodes. There we only one or two
On 06/15/2015 01:07 PM, Jay Pipes wrote:
It has come to my attention in [1] that the microversion spec for Nova
[2] and Ironic [3] have used the project name -- i.e. Nova and Ironic --
instead of the name of the API -- i.e. OpenStack Compute and
OpenStack Bare Metal -- in the HTTP header that
Madhuri,
On Jun 15, 2015, at 12:47 AM, Madhuri Rai
madhuri.ra...@gmail.commailto:madhuri.ra...@gmail.com wrote:
Hi,
Thanks Adrian for the quick response. Please find my response inline.
On Mon, Jun 15, 2015 at 3:09 PM, Adrian Otto
adrian.o...@rackspace.commailto:adrian.o...@rackspace.com
+1
Regards,
Daneyon Hansen
Software Engineer
Email: daneh...@cisco.com
Phone: 303-718-0400
http://about.me/daneyon_hansen
From: Steven Dake (stdake) std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
+1 for me as well. Designate looks great
On Jun 15, 2015 6:43 AM, Ryan Hallisey rhall...@redhat.com wrote:
+1 Great job with Cinder.
-Ryan
- Original Message -
From: Steven Dake (stdake) std...@cisco.com
To: OpenStack Development Mailing List (not for usage questions)
Hi Jay,
Cloudbreak is a Hadoop installation tool driven by Hortonworks. The main
difference with Sahara is a point of control. In Hortonworks world you have
Ambari and different planforms (AWS, OpenStack, etc.) to run Hadoop. Sahara
point of view - you have OpenStack cluster and want to control
1 - 100 of 169 matches
Mail list logo
