On 1 August 2015 at 05:16, Lucas Alvares Gomes lucasago...@gmail.com
wrote:
Hi,
It sounds like we all agree -- the client we ship should default to a
fixed,
older version. Anyone who wants newer functionality can pass a newer
version
to their client.
Here's the current state of
+1
On 18/08/15 07:37, Sahdev P Zala wrote:
Hello,
I am glad to nominate Vahid Hashemian [1] and Srinivas Tadepalli [2]
for the Heat-Translator core reviewers team.
Both of them have been providing significant contribution, development
and review, since the beginning of this year and knows
On Mon, Aug 17, 2015 at 5:19 PM, Clark Boylan cboy...@sapwetik.org wrote:
Just letting everyone know that Neutron have asked that changes to their
job configs (think project-config, devstack-gate, etc) be ACKed by one
of their Infra liasons (mestery, dougwig, and armax) before we merge it.
Hi all,
Gerrit (review.openstack.org) has been restarted and the systems are back
up and functioning.
We have an idea of the cause of the problem and will investigate more
permanent fixes.
Cheers,
Josh
On Mon, Aug 17, 2015 at 5:06 PM, Joshua Hesketh joshua.hesk...@gmail.com
wrote:
Hi all,
Hello,
In current design there are places when nova fails while executing users
CLI commands, but no error messages, except some logs in nova-compute,
produced [1] . The problem is that there is no response from compute node
to conductor, as RPC cast is used.
To fix this nova should make a
FYI, I have filed a bug to track this:
https://bugs.launchpad.net/nova/+bug/1485529
It'd be really nice to fix this in the L release.
Thanks,
Rado
On 4.08.2015 14:18, Radoslav Gerganov wrote:
There is an API (os-console-auth-tokens) which returns the connection
info which correspond to a
James E. Blair wrote:
As mentioned previously[1], we are retiring the stackforge/ namespace
for git repositories and creating new projects in openstack/. This is
largely a cosmetic change and does not change the governance model for
new projects.
As part of this we want to move all of the
Hi all,
Gerrit (review.openstack.org) has been restarted and the systems are back
up and functioning.
We have an idea of the cause of the problem and will investigate more
permanent fixes.
Cheers,
Josh
On Mon, Aug 17, 2015 at 5:06 PM, Joshua Hesketh joshua.hesk...@gmail.com
wrote:
Hi all,
Excerpts from Davanum Srinivas (dims)'s message of 2015-08-16 17:40:16 -0400:
Doug,
I've filed https://review.openstack.org/213542 to log error messages. Will
work with oslo.messaging folks the next few days.
Thanks, Dims!
Thanks,
Dims
On Fri, Aug 14, 2015 at 6:58 PM, Doug Hellmann
Hi OpenStack dev team,
we found issue [1] in Horizon (probably, in Nova API too), which blocks the
ability to boot VMs with option Instance Boot Source = Boot from image
(creates new volume) in case when we have several Availability Zones in
Nova and Cinder - it will fail with error Failure
Hello,
We currently plan to upgrade our Openstack setup from Icehouse to Juno or
even Kilo. This also includes a version upgrade on the host based OS from
Centos 6.6 to 7.x
I have some questions regarding the upgrade an hope to learn from your
experience.
First question is, is there a
Yes, I fully support this. Let’s do this.
Renat Akhmerov
@ Mirantis Inc.
On 13 Aug 2015, at 17:44, ELISHA, Moshe (Moshe)
moshe.eli...@alcatel-lucent.com wrote:
Hey,
Following our discussion in the IRC, when pushing UI changes please upload a
screenshot of the result and add a link
On 17 August 2015 at 20:45, Jesse Pretorius jesse.pretor...@gmail.com wrote:
Do we want to make it a default to True for users of DevStack? I think
it
may be worth considering since I'm not familiar with this issue with
crypto
and having something that protects devs who are trying to
Hi,
I can't find any way to change the image size of the vm used for testing
(it's been created using nodepool-dib and managed by nodepoold).
Anyway, tests are still (randomly) failing with lvm error (Volume group
stack-volumes-lvmdriver-1 has insufficient free space (1023 extents):
1024
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi VmWare folks,
I wonder whether we can get some actual release tags for stable/kilo
branch of the repo. Lack of any consumable tarballs does not help
packagers that want to just get the tarball from pypi and use it as a
base.
I tried to follow
Hi Team,
Thanks for attending the meeting and had a lively discussion on L2GW,
please find in the attachment for the meeting log.
Be noted that we will have the 2nd part of the meeting next Monday at the
same time. :)
On Mon, Aug 17, 2015 at 10:16 AM, Zhipeng Huang zhipengh...@gmail.com
wrote:
Hi,
It doesn't seem to help, install still fails with same error.
Thanks,
Eduard
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
HI Abhishek:
For you information in the below.
HI Mike:
What I have missed it?
On Mon, Aug 17, 2015 at 8:52 PM, Rick Chen rick.c...@prophetstor.com
mailto:rick.c...@prophetstor.com wrote:
HI Mike:
I completed to refine our CI configuration to follow Ramy's
On 08/15/2015 01:15 PM, Michael Krotscheck wrote:
On Fri, Aug 14, 2015 at 2:26 PM Adam Young ayo...@redhat.com
mailto:ayo...@redhat.com wrote:
On 08/14/2015 12:43 PM, Michael Krotscheck wrote:
1- Do users want to page through search results?
Does not matter: in Federation, the
Hello,
1) We have in total 4 separate clouds who need the upgrade with each
more than 100 compute nodes. We just use the basic services like nova,
keystone, neutron, glance and horizon. No Cinder, heat, trove etc.
Our network setup is flat provider network, which means we don't use the
On 2015-08-17 22:39:56 + (+), Mooney, Sean K wrote:
[...]
Assuming this was not intentional I have opened a bug and
submitted a patch to revert this change.
[...]
Fix https://review.openstack.org/213843 is already winding its way
through the sausage factory.
--
Jeremy Stanley
The only alternative seems to be to have on-demand stable-branch
tagging. The main drawbacks of that option are that consumers of the
stable branch are unnecessarily limited to specific tagged commits, and
depend on various project teams to remember to push them.
As Doug suggested, stable
On Mon, Aug 17, 2015 at 5:58 PM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-08-17 22:39:56 + (+), Mooney, Sean K wrote:
[...]
Assuming this was not intentional I have opened a bug and
submitted a patch to revert this change.
[...]
Fix https://review.openstack.org/213843 is
On 15/08/15 00:23, Rich Megginson wrote:
On 08/14/2015 06:51 AM, Matthew Mosesohn wrote:
Gilles,
I already considered this when looking at another openstackclient
issue. Version 1.0.4 has almost no changes from 1.0.3, which is the
official release for Kilo. Maybe we can get this keystone
Hello,
Do you have any recommendation for hardware based SDN products which are
compatible with openstack Neutron? It has the features like what Neutron
does, including Net/subnet/IP/Port management, vRouter etc.
Thanks.
___
Mailing list:
HI Adhishek:
One more information, how are you catching the logs and making it browsable?
Do you mean item[6]? I just follow OpenStack Third-part CI document.
You can reference
http://docs.openstack.org/infra/system-config/third_party.html#faq-frequently-asked-questions.
Add this
On Mon, Aug 17, 2015 at 03:51:46PM -0500, Matt Riedemann wrote:
What version of taskflow is installed? Cinder 2014.2.3 requires this
version of taskflow [1]:
taskflow=0.4,0.7.0
Which should get you taskflow 0.6.2, and taskflow 0.6.2 has this requirement
[2] for futures:
I think we've conveniently been led off track here. The original
request/subject was regarding pagination of projects in the v3 API. Since
this is purely a keystone construct it seems implausible to me that ldap or
the IdP of choice would be limiting the ability to return a paginated list
of all
On Aug 17, 2015, at 9:08 AM, Alex Xu hejie...@intel.com wrote:
We have weekly Nova API meeting this week. The meeting is being held tomorrow
Tuesday UTC1200.
In other timezones the meeting is at:
EST 08:00 (Fri)
Japan 21:00 (Fri)
China 20:00 (Fri)
United Kingdom 13:00 (Fri)
s/Fri/Tue
在 2015年8月18日，上午10:07，Ed Leafe e...@leafe.com 写道：
On Aug 17, 2015, at 9:08 AM, Alex Xu hejie...@intel.com wrote:
We have weekly Nova API meeting this week. The meeting is being held
tomorrow Tuesday UTC1200.
In other timezones the meeting is at:
EST 08:00 (Fri)
Japan 21:00 (Fri)
On 08/17/2015 09:53 PM, David Lyle wrote:
I think we've conveniently been led off track here. The original
request/subject was regarding pagination of projects in the v3 API.
Since this is purely a keystone construct it seems implausible to me
that ldap or the IdP of choice would be limiting
+1 for both.
From: Sahdev P Zala/Durham/IBM@IBMUS
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
Date: 08/17/2015 12:39 PM
Subject:[openstack-dev] [heat-translator] Nominating new core
reviewers
Hello,
I am glad to nominate
On 08/17/2015 09:29 PM, James Slagle wrote:
On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy sha...@redhat.com wrote:
Hi all,
Recently I had some discussion with folks around the future strategy for
TripleO wrt upgrades, releases and branches, specifically:
- How do we support a stable TripleO
Cool so its almost unanimous but all the core reviewers have weighed in.
Welcome to the Kolla Core Reviewer team Swapnil !
Regards
-steve
From: Martin André martin.an...@gmail.commailto:martin.an...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
Hi I just noticed the default review branch for neutron has been updated to the
feature/qos branch
Assuming this was not intentional I have opened a bug and submitted a patch to
revert this change.
https://bugs.launchpad.net/neutron/+bug/1485788
https://review.openstack.org/#/c/213908/
On 2015-08-18 01:36:05 +0200 (+0200), Alan Pevec wrote:
[...]
OSSA merge could trigger an async release proposal too.
True, now that we're putting the advisories through Gerrit, that's
certainly an available option.
--
Jeremy Stanley
I would check out Big Switch Networks. I'm biased because I worked there
:), but they have a full fabric integration with Neutron.[1]
1. http://www.bigswitch.com/sdn-products/big-cloud-fabrictm
On Tue, Aug 18, 2015 at 10:02 AM, Ken Peng kp...@runbox.com wrote:
Hello,
Do you have any
Paging support for certain Keystone constructs seems reasonable to me
(roles, domains and projects). But as Adam Young just wrote in [0], though
possible for our SQL backends, why? Do you really expect deployments to
have 100s of roles/domains/projects?
IMO groups probably should not have paging,
Excerpts from Alan Pevec's message of 2015-08-18 01:36:05 +0200:
The only alternative seems to be to have on-demand stable-branch
tagging. The main drawbacks of that option are that consumers of the
stable branch are unnecessarily limited to specific tagged commits, and
depend on various
On 11 August 2015 at 06:13, Ruby Loo rlooya...@gmail.com wrote:
Hi, sorry for the delay. I vote no. I understand the rationale of trying to
do things so that we don't break our users but that's what the versioning is
meant for and more importantly -- I think adding the ENROLL state is fairly
- Original Message -
It occurs to me that there has never been a detailed exposition of the
purpose of the tripleo-common library here, and that this might be a
good time to rectify that.
Basically, there are two things that it sucks to have in the client:
First, logic - that is,
On 2015-08-17 15:25:07 +0200 (+0200), Thierry Carrez wrote:
[...]
I see Doug, Robert, Clark and myself as necessary to the
discussion
[...]
It would also be great to get some of the operators and/or package
maintainers involved since they were the ones arguing against the
original and much
On 08/17/15 at 02:59pm, Timofei Durakov wrote:
Hello,
In current design there are places when nova fails while executing users
CLI commands, but no error messages, except some logs in nova-compute,
produced [1] . The problem is that there is no response from compute node
to conductor, as RPC
Hi All,
How do I implement one extension by two plugins?
If I extend the API by:
* a first class resource, and
* attributes to an already existing resource (the port resource in my case).
These two parts don't make sense without each other, so I'd like to
keep this as one extension, not two.
+1. Especially if you don't use fake mode of Nailgun, I don't know why
would you even be copying legacy code to the new repo..
Thanks!
On Mon, Aug 17, 2015 at 6:25 AM Jay Pipes jaypi...@gmail.com wrote:
On 08/17/2015 08:50 AM, Roman Prykhodchenko wrote:
Hi Fuelers!
I was working on
Hi,
We have weekly Nova API meeting this week. The meeting is being held tomorrow
Tuesday UTC1200.
In other timezones the meeting is at:
EST 08:00 (Fri)
Japan 21:00 (Fri)
China 20:00 (Fri)
United Kingdom 13:00 (Fri)
The proposed agenda and meeting details are here:
Hi Fuelers!
I was working on enabling Python tests in Fuel Client to run on OpenStack CI
and I figured out that we actually have a piece of legacy code which can be
removed now. That piece is run_tests.sh file. For those who’s not aware, that
script allows to run different tests under
Hi!
This discussion died without a clear way forward...
The automatically tagging every commit option, described by Robert as
the only sensible route, results according to Clark in so many tags
you end up polluting the ref space and making it unusable by humans.
However, we are lacking other
Thierry Carrez wrote:
Doug Hellmann wrote:
How detailed do we want release notes to be? For example, do we need to
worry about supporting multiple paragraphs or ASCII art or anything like
that?
Looking at our current release notes, they are a set of bullet points of
a pre-determined type.
On Mon, Aug 17, 2015 at 4:02 PM, Marc Pape marc.p...@gmail.com wrote:
the internal SQL . It would be great if the service users of OpenStack
are also stored in SQL, but they are also currently in the LDAP
deposited.
This is an use case for keystone domains
Hi,
We had our driver removed by commit:
https://github.com/openstack/cinder/commit/f0ab819732d77a8a6dd1a91422ac183ac4894419
due to no CI.
Last week we got it working again and it's been commenting for the last 3
days continuously.
A normal run looks like this:
*08:40:37* Ran: 1265 tests in
Hi,
I'm trying to support AWS signature version 4 for S3 requests.
Related bugs:[1] for keystonemiddleware and [2] for swift3:
Also keystone doesn't have support for V4 signature verification for S3
(but it supports V4 for EC2 requests).
Differences between V1 and V4 can be found here - V1: [3]
Well this can be very time consuming but first thing first
1) how is your installation done?
2) is this an HA env?
3) chaining from 6.x to 7 is good but may not play well
4) database schema changed from Icehouse to Juno so keep that in mind.
Then you can start thinking on the upgrades. I know
Maybe its best to also send this to the Ryu mailing list
On Mon, Aug 17, 2015 at 4:31 PM, Vikram Choudhary
vikram.choudh...@huawei.com wrote:
Widening audience!
*From:* Vikram Choudhary [mailto:vikram.choudh...@huawei.com]
*Sent:* 17 August 2015 18:05
*To:*
Hi,
As far as I understand we have a base agreement that both specs are
appropriate and either of that two features are shifted to Mitaka cycle.
Gordon probably that question to you:
Are we going to create a new folder in spec's dir for next cycle, or we
continue discussing new specs as part of
BTW, the similar situation is with FWaaS [1]
[1] https://bugs.launchpad.net/neutron/+bug/1485509
On Fri, Aug 7, 2015 at 4:07 AM, shihanzhang ayshihanzh...@126.com wrote:
I have same question, I have filed a bug on launchpad:
https://bugs.launchpad.net/neutron/+bug/1476469,
who can help to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/17/2015 04:35 PM, Bence Romsics wrote:
Hi All,
How do I implement one extension by two plugins?
If I extend the API by: * a first class resource, and * attributes
to an already existing resource (the port resource in my case).
These
puppet-ceilometer is in fact broken for the same reason oh puppet-horizon,
so no action required, we just need to wait for
https://review.openstack.org/213688 got merged.
On Mon, Aug 17, 2015 at 8:31 AM, Emilien Macchi emilien.mac...@gmail.com
wrote:
So we bumped our CI to Liberty last week,
Hi,
This is a reminder that we’ll have a team meeting today at #openstack-meeting
at 16.00 UTC time.
The agenda:
Review action items
Current status (progress, issues, roadblocks, further plans)
Liberty-3 progress
New meeting time
Open discussion
Add your items whether by replying to this email
Thierry Carrez wrote:
We need to make progress on this so that the tooling is ready when we
switch to stable branches at the end of Liberty. Should we discuss it
live at a cross-project meeting ? I see Doug, Robert, Clark and myself
as necessary to the discussion, but anyone else is welcome to
Thanks for the information.
On 17-Aug-2015 7:53 pm, Gal Sagie gal.sa...@gmail.com wrote:
Maybe its best to also send this to the Ryu mailing list
On Mon, Aug 17, 2015 at 4:31 PM, Vikram Choudhary
vikram.choudh...@huawei.com wrote:
Widening audience!
*From:* Vikram Choudhary
I have the impression that more and more people try to run OpenStack
in a mixed-releases-mode and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of [1] runs a nova-conductor (Juno) with a nova-compute (Kilo). I tried
in comment #3 of [1]
Widening audience!
From: Vikram Choudhary [mailto:vikram.choudh...@huawei.com]
Sent: 17 August 2015 18:05
To: ryu-de...@lists.sourceforge.net
Cc: Tidwell, Ryan; Vikram Choudhary; Jaume Devesa; Numan Siddique; Kalyankumar
Asangi; Baldwin, Carl (OpenStack Neutron)
Subject: [Ryu-devel] [IMPORTANT]:
Hi,
During last week's Firewall as a Service IRC meeting, we discussed the
possibility of having an Asia-Pacific timezone friendly meeting. If you
are in that timezone - please let me know what time (UTC) works.
I am US EST, and we have a lot of US PST attendees (I think) - so here's what
is
On 08/17/2015 08:50 AM, Roman Prykhodchenko wrote:
Hi Fuelers!
I was working on enabling Python tests in Fuel Client to run on
OpenStack CI and I figured out that we actually have a piece of
legacy code which can be removed now. That piece is run_tests.sh
file. For those who’s not aware, that
Hi all,
Recently I had some discussion with folks around the future strategy for
TripleO wrt upgrades, releases and branches, specifically:
- How do we support a stable TripleO release/branch that enables folks to
easily deploy the current stable release of OpenStack
- Related to the above,
Most of openstack services use ProcessLauncher(located in oslo.services)
to run services, fork new worker processes, reload configuration, etc.
Initialization of services in master process usually contains opening of
sockets, so that socket will be inherited in child processes. Then
So we bumped our CI to Liberty last week, and added logs support in our
jobs ( https://goo.gl/8ncRHi )
But now, we have some failures:
* puppet-horizon: log publisher is broken for apache, we need
https://review.openstack.org/213688 merged and the dsvm image updated - no
action required from our
On 2015-08-17 14:05:38 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
I tried to follow the dumb way of generating a tarball from github,
but pbr complains about lack of sdist or git when I call to 'setup.py
build'. Putting egg-info directory inside the tarball does not help.
In a clean checkout
Hello everybody,
i've got some problems with our OpenStack (Juno) and the Integrate
Identity Service over LDAP.
The LDAP connection is read only, so i configured the [identity],
[ldap] and [assignment] parts in keystone conf.
The identity part use driver =
keystone.identity.backends.ldap.Identity
As a follow-up to the recent development ML thread on scaling back
release management workload for stable branches[1], a deep-dive
discussion is planned to talk through potential solutions during
tomorrow's Cross-Project Meeting[2]. Parties with a particular
interest in solving this are encouraged
HI Adhishek:
I add “AllowOverride all” option and point to the OpenStack CI log
folder in the apache configuration.
Directory /var/log/prophetstor_ci
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
/Directory
and set the .htaccess file
Also adding the following:
-
https://github.com/openstack-infra/project-config/tree/master/nodepool/elements
Does this means that we don't have to take care of creating slaves(i.e;
installing slave using scripts as we have done in master) and it will be
done automatically, and also we
Also adding the following:
-
https://github.com/openstack-infra/project-config/tree/master/nodepool/elements
Does this means that we don't have to take care of creating slaves(i.e;
installing slave using scripts as we have done in master) and it will be
done automatically, and also we
Hi Folks,
I was going through Ramy's guide for setting up CI, there I found out the
following:
-
https://github.com/rasselin/os-ext-testing#setting-up-nodepool-jenkins-slaves
But I don't get the fact on how to create the image, also what major
settings need to be done to make the config
Hi Folks,
I was going through Ramy's guide for setting up CI, there I found out the
following:
-
https://github.com/rasselin/os-ext-testing#setting-up-nodepool-jenkins-slaves
But I don't get the fact on how to create the image, also what major
settings need to be done to make the config
On 08/17/2015 08:59 AM, Jay Pipes wrote:
On 08/17/2015 10:41 AM, Markus Zoeller wrote:
I have the impression that more and more people try to run OpenStack
in a mixed-releases-mode and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of
Hi,
Starting last week, we are no longer alternating meeting times. Going
forward, the ironic meetings will be held weekly on Mondays at 1700 UTC.
(For more information on our weekly meetings, see [0]).
There had been a friendly discussion about this [1] and it was mentioned in
last week's
A *summary* of the Cinder midcycle sprint, in attempt to keep your attention.
Full meeting notes available [1].
Image Caching
=
Glance Cinder backend store + Cinder Image Caching are so similar, it would
just be confusing to operators. We'll document only about the Cinder Image
Thanks for joining us today for the meeting.
Meeting minutes:
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-08-17-16.02.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-08-17-16.02.html
Meeting log:
Hi,
The driver name should be kvm and not qemu.
interface type=hostdev managed=yes
mac address=fa:16:3e:eb:38:da/
driver name=qemu/
source
address type=pci domain=0x bus=0x81 slot=0x02
function=0x7/
/source
vlan
tag id=1009/
/vlan
Hi,
There are still a few extra stable back ports that we need to make.
In addition to this I think that we should try and sync all of the etrnal
projects for a common release.
Thanks
Gary
From: mest...@mestery.commailto:mest...@mestery.com
mest...@mestery.commailto:mest...@mestery.com
Gordon thanks for quick answer.
I'll add a patch with new dir for mitaka specs and move my specs there.
cheers,
Igor Degtiarov
Software Engineer
Mirantis Inc.
www.mirantis.com
On Mon, Aug 17, 2015 at 7:02 PM, gord chung g...@live.ca wrote:
good questions...
On 17/08/2015 10:19 AM, Igor
On Mon, Aug 17, 2015 at 7:42 AM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-08-17 14:05:38 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
I tried to follow the dumb way of generating a tarball from github,
but pbr complains about lack of sdist or git when I call to 'setup.py
build'.
1. yes, but probably only if its a short list. It may be feasible to show it
only if there are 5 or less pages, and maybe just load all pages of data and
paginate it on the client. If too big, ask the user to refine their search? Or
always paginate to 5, and then the 6th page have a page
I've pushed the patch into the merge queue now. Any nits people find at
this point we'll address post merge.
Awesome work QoS team!
On Mon, Aug 17, 2015 at 9:56 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
So the patch in question sit there
I'd like to announce networking-calico, a new project within the Neutron
stadium to provide OpenStack integration pieces for Project Calico
[1][2]. In a sentence, Calico is a backend that uses routing and
iptables to provide IP-level connectivity between VMs, instead of - as
most Neutron backends
+ I've just discussed UX for Ubuntu bootstrap in #fuel-dev [1], which
doesn't look very clear at the moment.
Mikhail - can you please help to clear it up? Namely, can I build Ubuntu
bootstrap on Fuel master without direct Internet access? How can I trigger
its build (is it from Fuel menu or from
On Mon, Aug 17, 2015 at 7:05 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi VmWare folks,
I wonder whether we can get some actual release tags for stable/kilo
branch of the repo. Lack of any consumable tarballs does not help
packagers
Hi all,
what is the current status of the feature in terms of readiness for
production use? I'm wondering as I see a number of bugs, and so we might
want to still have it in experimental mode for 7.0, and enable in 8.0.
These are the bugs I came across:
[1]
No, that's not valid behaviour. You need to upgrade the controller
infrastructure (conductor, API nodes, etc) before any compute nodes.
Yep.
--Dan
signature.asc
Description: OpenPGP digital signature
__
OpenStack
HI Mike:
I completed to refine our CI configuration to follow Ramy's
comments. Does any missed or other attention I need respect?
[1] Add export DEVSTACK_GATE_TEMPEST_REGEX=volume to verify all
cinder volume testing.
[2] Add each service configuration in the log.
Dan Smith d...@danplanet.com wrote on 08/17/2015 05:08:25 PM:
From: Dan Smith d...@danplanet.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 08/17/2015 05:15 PM
Subject: Re: [openstack-dev] [nova] compute - conductor and version
Hi,
I am new to Barbican and try to understand what it would take to implement
the crypto plugin API.
Could someone please point me to the right interface definition, and an
example plugin?
Thanks
Andy
Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research
Le 29/07/2015 10:27, Robert Collins a écrit :
Similar to pbr, we have a minimum version of setuptools required to
consistently install things in OpenStack. Right now thats 17.1.
However, we don't declare a setup_requires version for it.
I think we should.
If it's possible to explicit the
Hi,
The driver name should be kvm and not qemu.
interface type=hostdev managed=yes
mac address=fa:16:3e:eb:38:da/
driver name=qemu/
source
address type=pci domain=0x bus=0x81 slot=0x02
function=0x7/
/source
vlan
tag id=1009/
/vlan
On 08/17/2015 10:41 AM, Markus Zoeller wrote:
I have the impression that more and more people try to run OpenStack
in a mixed-releases-mode and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of [1] runs a nova-conductor (Juno) with a
I remembered I saw somewhere about how to upgrade, (step by step in
updating from J to K or others)
I think it's best and suitable way to use this kind of 'different version'
talking to make compute host alive
during system upgrade.
so I believe controller should be upgrade first the compute
On 17 August 2015 at 15:59, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-08-17 15:46:24 +0200 (+0200), Thierry Carrez wrote:
[...]
OSSA: -ZZZ
For commits that correspond to vulnerability fixes.
[...]
I don't think that's going to be feasible. Consider the sequence
with a public
Hi,
I have an HA openstack setup with haproxy and neutron networking.
Sometimes, when we need to work on the haproxy nodes and need to
shutdown the haproxy (we are still testing things), metadata breaks.
Actually metadata breaks a lot, easily and quite often. It's probably
the most fragile
1 - 100 of 146 matches
Mail list logo
