On 27 August 2015 at 02:15, Ihar Hrachyshka ihrac...@redhat.com wrote:
I really wish that nothing of this kind was even possible. Adding
such an upper cap is like hiding the dust under the carpet: it
doesn't remove the issue, it just hides it. We really have too much
of these in OpenStack.
On 27 August 2015 at 01:31, Thomas Goirand z...@debian.org wrote:
On 08/25/2015 11:20 PM, Robert Collins wrote:
So I can't upload PBR 1.3.0 to Sid. This has been dealt with
because I am the maintainer of PBR, but really, it shouldn't have
happen. How come for years, upgrading PBR always
On 07/28/2015 09:00 AM, Kekane, Abhishek wrote:
Hi Devs,
There is an NFS backend driver for cinder, which supports only limited
volume handling features. Specifically, snapshot and cloning
features are missing.
Eric Harney has proposed a feature of NFS driver snapshot [1][2][3],
On 27 August 2015 at 02:00, Gareth academicgar...@gmail.com wrote:
Hey guys,
I have a question about dependencies. There is an example:
On 2014.1, project A is released with its dependency in requirements.txt
which contains:
foo=1.5.0
bar=2.0.0,2.2.0
and half a year later, the
I've been working with Nova's versioned objects lately to help catch
people when object changes are made. There is a lot of object-related
tests in Nova for this, and a major one I can see helping this situation
is this test [1]. Looking through the different versioned objects within
Magnum, I
Tony,
Thanks for digging into this!
I should be able to help, but right now we're ramping up for the L3
feature freeze and there are a lot of release-related activities going
on. Can this wait a few weeks for things to settle down again?
Doug
Excerpts from Tony Breeds's message of 2015-08-24
On Wed, Aug 26, 2015 at 05:28:47PM +0200, Jan Provazník wrote:
Hi,
although rdomanager-oscplugin is not yet under TripleO it should be soon, so
sending this to TripleO audience.
Satellite registration from user's point of view is now done by passing
couple of specific parameters when
- Original Message -
From: Jay Dobies jason.dob...@redhat.com
To: openstack-dev@lists.openstack.org
Sent: Tuesday, 25 August, 2015 2:31:02 PM
Subject: Re: [openstack-dev] [TripleO] Encapsulating logic and state in the
client
Thinking about this further, the interesting question
Hi all,
I’m trying to stand up magnum according to the quickstart instructions with
devstack.
There’s one resource which times out and fails: master_wait_condition. The kube
master (fedora) host seems to be created, I can login to it via ssh, other
resources are created successfully.
What
[If any of this is wrong I hope someone from infra or qa will
correct me. Thanks. This feels a bit cumbersome so perhaps there is
a way to do it in a more automagic fashion[1].]
In the near future ceilometer will be removing itself from the core
of devstack and using a plugin instead. This is
On 24/08/15 18:37 +0300, Alexander Tivelkov wrote:
Hi folks,
In the upcoming L release Murano is going to use the Glance Artifact
Repository feature implemented as part of EXPERIMENTAL Glance V3 API.
The server-side support of this feature is already merged in glance's master
branch, while the
We considered that option and have finally agreed on what Alex suggests
at the rel-mgrs office as this is the least painful path for most.
On 8/26/15 12:04 PM, Flavio Percoco wrote:
On 24/08/15 18:37 +0300, Alexander Tivelkov wrote:
Hi folks,
In the upcoming L release Murano is going to use
I think that if we’ve got someone identified to do the ref implementation, and
that is code complete by 8/31, we can apply for a feature freeze exception. If
we don’t have someone assigned to that task, it’ll slip.
doug
On Aug 26, 2015, at 7:22 AM, Samuel Bercovici samu...@radware.com wrote:
On 26/08/15 12:22 -0400, Nikhil Komawar wrote:
We considered that option and have finally agreed on what Alex suggests
at the rel-mgrs office as this is the least painful path for most.
It would have been nice to know it had already been discussed across
some glance members and other folks.
Hi,
As Sam mentioned, I will join Octavia meeting today, hope there will be time to
discuss L7 tasks
L7 related patches in review now are:
Extension https://review.openstack.org/#/c/148232
CLI https://review.openstack.org/#/c/217276
Reference implementation
On 26/08/15 19:30 +0200, Flavio Percoco wrote:
Greetings,
I'm happy to announce that the Zaqar team will hold a testing day this
Friday, August 28th. We'll be testing the API and the client library
and the hope is to find as many issues as possible that can be fixed
before our next release.
On Wed, Aug 26, 2015 at 8:18 AM, Matt Riedemann mrie...@linux.vnet.ibm.com
wrote:
On 8/26/2015 3:21 AM, Timofei Durakov wrote:
Hello,
Here is the situation: nova has live-migration feature but doesn't have
ci job to cover it by functional tests, only
Update:
1. Job fails from time to time, I'm collecting statistics to understand
whether it is valid fails or some races, etc.
2. This sounds good:
jogo has had a patch up for this for awhile:
https://review.openstack.org/#/c/165233/
3. It's required more research:
We already have a voting
Gareth,
A real example is to enable Rally for OpenStack Juno. Rally doesn't support
old release officially but I could checkout its codes to the Juno release date
which make both codes match. However even if I use the old requirements.txt
to install dependencies, there must be many packages
Can't find the logs on eavesdrop atm. Discussed yesterday on
#openstack-relmgr-office around UTC evening.
On 8/26/15 12:32 PM, Flavio Percoco wrote:
On 26/08/15 12:22 -0400, Nikhil Komawar wrote:
We considered that option and have finally agreed on what Alex suggests
at the rel-mgrs office as
Greetings,
I'm happy to announce that the Zaqar team will hold a testing day this
Friday, August 28th. We'll be testing the API and the client library
and the hope is to find as many issues as possible that can be fixed
before our next release.
I'd like to extend the invitation to the entire
Greetings Heat/Horizon Devs,
There is some talk about possibly backward-incompatible changes to the
Neutron VPNaaS API and I'd like to better understand what that means for
Heat and Horizon.
It has been proposed to change Neutron VPNService objects such that they
reference a new resource type
On Wed, Aug 26, 2015 at 03:11:56PM -0400, Doug Hellmann wrote:
Tony,
Thanks for digging into this!
No problem. It seemed like such a simple thing :/
I should be able to help, but right now we're ramping up for the L3
feature freeze and there are a lot of release-related activities going
On 08/26/2015 04:25 PM, Amitabha Biswas wrote:
With the recent commits it seems that the
gate-tempest-dsvm-networking-ovn is succeeding more or less every time.
The DBDeadlock issues still are seen on q-svc logs but are not frequent
enough to cause ovsdb failures that were leading to the
My apologies for not expressing my thoughts on this matter
sooner, however I've had to spend some time collecting my
thoughts.
To me, it seems like we do not trust our users. Granted,
when I say users, I mean administrators who likely know more
about the disposition and capabilities of their
Hi Everyone,
There is a pending change up for review that will move the location subunit2html
jenkins slave script:
https://review.openstack.org/212864/
It switches from a locally installed copy to using the version packaged in
os-testr which is installed in a system venv. This was done in an
hey Saharans,
with Doc fix day fast approaching i wanted to send out an email with the
etherpad again,
https://etherpad.openstack.org/p/sahara-liberty-doc-update-day
it has been updated with all the docs and we are ready to roll starting
on monday aug 31.
mike
On 08/24/2015 09:41 AM,
On 08/25/2015 07:38 PM, Chris Dent wrote:
WSME version 0.8.0 was released today with several fixes to error
handling and error messages. These fixes make WSME behave more in
the way it says it would like to behave (and should behave) with
regard to input validation and HTTP handling. You want
Hi all,
When SR-IOV introduce in Juno the SR-IOV Agent supported only link state change.
Some Intel cards don't support setting link state, so to
resolve it the SR-IOV mechanism driver supports agent and agent less mode.
From Liberty the SR-IOV agent brings more functionality like
qos and port
Chris,
What would be your recommendation for now? Just to cap wsme version and hold on
with changes adjusting to WSME 0.8.0? Or you think most likely these changes in
new WSME will remain on?
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 26 Aug 2015, at 14:27, Chris Dent chd...@redhat.com
Hi,
I noticed that right now, when we make changes (adding/removing fields) in
https://github.com/openstack/magnum/tree/master/magnum/objects , we don't
change object versions.
The idea of objects is that each change in their fields should be versioned,
documentation about the change should
On Wed, 26 Aug 2015, Dmitry Tantsur wrote:
Note that this is an API breaking change, which can potentially break random
users of all projects using wsme. I think we should communicate this point a
bit louder, and I also believe it should have warranted a major version bump.
Yeah, Lucas and I
Hi
With keystone, we recently came across an issue in terms of the assumptions
that the openstack client is making about the entities it can show - namely
that is assumes all entries have a ‘name’ attribute (which is how the
openstack show command works). Turns out, that not all keystone
Dmitry Borodaenko wrote:
TL;DR was actually hidden in the middle of the email, here's an even
shorter version:
0) we're suffering from closing master for feature work for too long
1) continuously rebased future branch is most likely a no-go
2) short FF (SCF and stable branch after 2
Martinx - ジェームズ wrote:
I'm proud to announce an Ansible Playbook to deploy OpenStack on Ubuntu!
Check it out!
* https://github.com/sandvine/os-ansible-deployment-lite
How does it compare with the playbooks developed as an OpenStack project
by the OpenStackAnsible team[1] ?
Any benefit,
On 26 Aug 2015, at 13:40, Dmitry Tantsur dtant...@redhat.com wrote:
On 08/25/2015 07:38 PM, Chris Dent wrote:
WSME version 0.8.0 was released today with several fixes to error
handling and error messages. These fixes make WSME behave more in
the way it says it would like to behave (and
Hi,
I see that we already have a magnum ui team, just wondering what is the
current status of this project? I'm planning a PoC and want to see if there
are some current magnum ui work that I can leverage.
--
Thanks,
Jay Lau (Guangya Liu)
Hi,
+1, yeah I kinda agree with the major version bump. But also it's
important to note that Ironic which was affected by that was relying
on be able to POST nonexistent fields to create resources and WSME
would just ignore those on versions = 0.8.0. That's a legitimate bug
that have been
Since it provides an opportunity to do some interesting things I
thought I should announce that ceilometer has left the core of
grenade and is now running its own 'gate-grenade-dsvm-ceilometer'
job that uses a grenade plugin hosted in the ceilometer repo.
At the moment the plugin does the bare
On 25/08/15 06:01 -0400, Davanum Srinivas wrote:
Morgan,
Bit more radical :) I am inclined to just yank all code from oslo-incubator and
let the projects modify/move what they have left into their own package/module
structure (and change the contracts however they see fit).
Glad this
Hi, Chris,
Thanks for bringing this up, and let us know. The same issues also affected
Mistral :-(
On Wed, Aug 26, 2015 at 1:38 AM, Chris Dent chd...@redhat.com wrote:
WSME version 0.8.0 was released today with several fixes to error
handling and error messages. These fixes make WSME behave
On Wed, 26 Aug 2015, Ryota Mibu wrote:
Quick note to ceilometer folks.
Many check and gate jobs for ceilometer are failed due to WSME related
issue that is already addressed by [1], so please make sure your patch
set are rebased on the current master before execute 'recheck'.
Thanks for
Hi,
Maybe I missed some key points. But why we introduced vpn-endpoint groups
here?
ipsec-site-connection for IPSec VPN only, gre-connection for GRE VPN
only, and mpls-connection for MPLS VPN only. You see, different
connections for different vpn types. Indeed, We can't reuse connection API.
On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote:
On Wed, 26 Aug 2015, Dmitry Tantsur wrote:
Note that this is an API breaking change, which can potentially break
random users of all projects using wsme. I think we should communicate this
point a bit louder, and I also
Ok, thanks. We’ll fix it in Mistral accordingly.
Renat Akhmerov
@ Mirantis Inc.
On 26 Aug 2015, at 15:12, Dmitry Tantsur dtant...@redhat.com wrote:
On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote:
On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote:
On Wed, 26 Aug 2015,
Flavio Percoco wrote:
On 25/08/15 06:01 -0400, Davanum Srinivas wrote:
Morgan,
Bit more radical :) I am inclined to just yank all code from
oslo-incubator and
let the projects modify/move what they have left into their own
package/module
structure (and change the contracts however they see
yep ttx. this will be for Mitaka.
-- Dims
On Wed, Aug 26, 2015 at 6:18 AM, Thierry Carrez thie...@openstack.org
wrote:
Flavio Percoco wrote:
On 25/08/15 06:01 -0400, Davanum Srinivas wrote:
Morgan,
Bit more radical :) I am inclined to just yank all code from
oslo-incubator and
let
Thierry, Dmitry,
key point is that we in Fuel need to follow as much community adopted
process as we can, and not to introduce something Fuel specific. We
need not only to avoid forking code, but also to avoid forking
processes and approaches for Fuel.
Both #2 and #3 allow it, making it easier
See @PCM inline...
On Wed, Aug 26, 2015 at 4:44 AM Germy Lure germy.l...@gmail.com wrote:
Hi,
Maybe I missed some key points. But why we introduced vpn-endpoint groups
here?
@PCM For the multiple local subnet capabilities for IPSec, the existing API
would need to be changed, so that we
James,
Great stuff! Please see @PCM in-line...
On Tue, Aug 25, 2015 at 6:26 PM James Dempsey jam...@catalyst.net.nz
wrote:
Oops, sorry about the blank email. Answers/Questions in-line.
On 26/08/15 07:46, Paul Michali wrote:
Previous post only went to dev list. Ensuring both and adding a
Hi,
This was a bit of a mistake on my part, I recently put together some
hardware in my home lab to try and rebuild a lab that is similar to the
lab I had, where I developed the support for provider networking, which
was documented in the following guide:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/26/2015 03:34 PM, Thomas Goirand wrote:
On 08/25/2015 08:59 PM, Matt Riedemann wrote:
On 8/25/2015 10:04 AM, Thomas Goirand wrote:
On 08/25/2015 03:42 PM, Thomas Goirand wrote:
Hi, [...] Anyway, the result is that mock 1.3 broke 9
The last python-novaclient release (2.26.0) was released on 6/3. Soft
dependency freeze is Thursday 9/3. So we plan on doing a
python-novaclient 2.27.0 release on Tuesday 9/1.
As of today, this is the list of changes since 2.26.0:
http://paste.openstack.org/show/428347/
Andrey requested
This seems quite reasonable. +1
Sent via mobile
On Aug 25, 2015, at 13:30, Rich Megginson rmegg...@redhat.com wrote:
This concerns the support of the names of domain scoped Keystone resources
(users, projects, etc.) in puppet.
At the puppet-openstack meeting today [1] we decided that
Ah, I did not have enough coffee, my control node wasn't synced and
didn't pick up PHYSICAL_NETWORK - that'll do it. Now I look like a
moron.
Sorry for the panic I may have caused
--
Sean M. Collins
__
OpenStack Development
Excerpts from Robert Collins's message of 2015-08-19 11:04:37 +1200:
On 18 August 2015 at 01:46, Thierry Carrez thie...@openstack.org wrote:
Following on from the IRC discussion about release notes.
ttx * we want consumers of the stable branch (from random commit
and from tagged versions)
Hi,
Recently when working on a simple bug [1] I've run into a need to change
rootwrap filters rules for a few commands. After sending fix to Gerrit [2] it
turns out that when testing the upgraded cloud grenade haven't copied my
updated volume.filters file, and therefore failed the check. I
Hey guys,
I have a question about dependencies. There is an example:
On 2014.1, project A is released with its dependency in requirements.txt
which contains:
foo=1.5.0
bar=2.0.0,2.2.0
and half a year later, the requirements.txt changes to:
foo=1.7.0
bar=2.1.0,2.2.0
It looks fine, but
Hello,
Here is the situation: nova has live-migration feature but doesn't have ci
job to cover it by functional tests, only
gate-tempest-dsvm-multinode-full(non-voting,
btw), which covers block-migration only.
The problem here is, that live-migration could be different, depending on
how instance
Hi Stanislaw,
Your host with Fedora should have special config file, which will send
signal to WaitCondition.
For good example please take a look this template
https://github.com/openstack/heat-templates/blob/819a9a3fc9d6f449129c8cefa5e087569340109b/hot/native_waitcondition.yaml
On Wed, 26 Aug 2015, Renat Akhmerov wrote:
What would be your recommendation for now? Just to cap wsme version
and hold on with changes adjusting to WSME 0.8.0? Or you think most
likely these changes in new WSME will remain on?
The fixes in WSME are fixes for genuine bugs. If code using WSME
On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote:
On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote:
On Wed, 26 Aug 2015, Dmitry Tantsur wrote:
Note that this is an API breaking change, which can potentially break
random users of all projects using wsme. I think we should
Hi,
I think that Evgeny is trying to complete everything bedsides the reference
implementation (API, CLI, Tempest, etc.).
Evgeny will join the Octavia IRC meeting so it could be a good opportunity to
get status and sync activities.
As far as I know 8/31 is feature freeze and not code complete.
On 08/25/2015 03:02 PM, Assaf Muller wrote:
On Tue, Aug 25, 2015 at 2:15 PM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
On 08/25/2015 01:26 PM, Amitabha Biswas wrote:
Russell suggested removing the MYSQL_DRIVER=MySQL-python declaration
from
On 08/25/2015 08:59 PM, Matt Riedemann wrote:
On 8/25/2015 10:04 AM, Thomas Goirand wrote:
On 08/25/2015 03:42 PM, Thomas Goirand wrote:
Hi,
[...]
Anyway, the result is that mock 1.3 broke 9 packages at least in Kilo,
currently in Sid [1]. Maybe, as packages gets rebuilt, I'll get more
On 08/26/2015 05:14 AM, Chris Dent wrote:
Since it provides an opportunity to do some interesting things I
thought I should announce that ceilometer has left the core of
grenade and is now running its own 'gate-grenade-dsvm-ceilometer'
job that uses a grenade plugin hosted in the ceilometer
+1 I'd love to know this too.
Additionally, if vagrant is something that is important to folks in the greater
community it would be great to get some of those bits upstreamed.
Per the NFV options, I don't see much in the way of OSAD not being able to
support that presently, its really a
On 8/26/2015 9:15 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/26/2015 03:34 PM, Thomas Goirand wrote:
On 08/25/2015 08:59 PM, Matt Riedemann wrote:
On 8/25/2015 10:04 AM, Thomas Goirand wrote:
On 08/25/2015 03:42 PM, Thomas Goirand wrote:
Hi, [...]
On 8/26/2015 3:21 AM, Timofei Durakov wrote:
Hello,
Here is the situation: nova has live-migration feature but doesn't have
ci job to cover it by functional tests, only
gate-tempest-dsvm-multinode-full(non-voting, btw), which covers
block-migration only.
The problem here is, that
On 08/26/2015 09:57 AM, Dulko, Michal wrote:
Hi,
Recently when working on a simple bug [1] I've run into a need to change
rootwrap filters rules for a few commands. After sending fix to Gerrit [2] it
turns out that when testing the upgraded cloud grenade haven't copied my
updated
On 08/25/2015 11:20 PM, Robert Collins wrote:
This first happened with PBR. Kilo can't use = 1.x
This is due to Kilo having *inappropriate* version caps on its
dependencies. Which we've been busy unwinding and fixing
infrastructure this cycle to avoid having it happen again on Liberty.
With the recent commits it seems that the gate-tempest-dsvm-networking-ovn
is succeeding more or less every time. The DBDeadlock issues still are
seen on q-svc logs but are not frequent enough to cause ovsdb failures
that were leading to the dsvm-networking failing before.
Once in a while a
Dmitry, thank you for getting our conversations and opinions spread across
different communications channels collected here in one cohesive email.
I like Ruslan's summary, and I support every line of what Ruslan has
written here.
Note that the two weeks is not really a hard requirement (could
Wow!
And changed the plugin.sh file back to original. However, with a cleaned
devstack (./unstack.sh, ./clean.sh, and removed /opt/stack) I still got the
error I mentioned in my previous post. Full stack log is attached.
Looks like I’ve found this tricky one ;)
In your log:
2015-08-26
Hi Victor,
Thanks for pointing out the issue with earlier deployment. Since I took
your advice I don't run into that problem again.
And thanks for the pointer on how to restart murano daemons. I think I
understand how to change murano code and test my changes locally.
I have one more question:
Hey!
the code does not seem to be inside the murano git repository, but under
python-muranoclient.
The code of murano-api located here [1]. The client is just a client for using
murano api functions from python ;)
But I don't see python-muranoclient files under my deployed devstack
True. This
On 26/08/15 23:43, Paul Michali wrote:
James,
Great stuff! Please see @PCM in-line...
On Tue, Aug 25, 2015 at 6:26 PM James Dempsey jam...@catalyst.net.nz
SNIP
1) Horizon compatibility
We run a newer version of horizon than we do neutron. If Horizon
version X doesn't work with
Hey Everyone,
John Villalovos and I have been acting as the Nova-Ironic liaisons, which
mostly means dealing with bugs that have been raised against the Ironic
driver in Nova. So you can understand what we’ve been doing, and how you
can help us do that job better, we’re writing this email to
Hi folks,
due to the upcoming soft dependencies the 0.11.0 release of sahara client
is planned to early next week, so, please review not yet merged changes.
If there are any patches you that you think should definitely become part
of this release, please, ping me in IRC / mail.
Thanks.
P.S. it
For details on the API/resource change, see the developer's reference
document that is under review: https://review.openstack.org/#/c/191944/
There is a section at the end, where I'm proposing a possible way to
support both versions of the API and provide backward compatibility. Feel
free to
Once in a while a test fails for e.g.
tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcpv6_two_subnets
that failed recently in Jenkins. But I am pretty sure it will succeed if
the suite is re-run.
Have you looked to see if the same test is failing for the regular
neutron
Hi Nikola,
Thank you for update.
Abhishek Kekane
-Original Message-
From: Nikola Đipanov [mailto:ndipa...@redhat.com]
Sent: 27 August 2015 01:10
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [cinder][nova] snapshot and cloning for NFS backend
On 07/28/2015 09:00
Hello, Ihar and Doug and Oslo team members,
I'm Daisuke Fujita,
The reason why I am writing this email to you is I'd like you to do a code
review.
Please visit followings which I uploaded.
https://review.openstack.org/#/c/216496/
https://review.openstack.org/#/c/216506/
Hi Shihanzhang,
Sorry for the late reply.
Later after asking for suggestion here on mailing list and while i was
exploring on how to fix this issue, bug was marked duplicate of
https://bugs.launchpad.net/neutron/+bug/1399249 . So i left its tracking.
And on your question, yes even after
Thanks Ganesh and Adrian.
I got it resolved.
Reason was that from inside master node openstack services were not
reachable.Openstack services were running on 127.0.0.1 as i had set HOST_IP
as 127.0.0.1 in localrc.As master could reach public network only and
127.0.01 was not reachable.I restacked
Hi Folks,
I am following Ramy's new guide for setting up the CI. Till now I have
installed master and created the slave node image using [1]. Now I want to
upload the image to nodepool, so can I use [2] to do so, or is there any
other way also to do so.
- Also is there any other changes that
Hi,
although rdomanager-oscplugin is not yet under TripleO it should be
soon, so sending this to TripleO audience.
Satellite registration from user's point of view is now done by passing
couple of specific parameters when running openstack overcloud deploy
command [1]. rdomanager-oscplugin
Hi Abhi,
First, using DIB is generally easier. However to use the scripts, you configure
nodepool to do so.
You should already have the scripts directory set [1]
Then you configure the script as the starting point for the image-build via
setup: prepare_node.sh [2]
Be sure to correctly
On Wed, Aug 26, 2015 at 4:23 AM, Igor Marnat imar...@mirantis.com wrote:
Thierry, Dmitry,
key point is that we in Fuel need to follow as much community adopted
process as we can, and not to introduce something Fuel specific. We
need not only to avoid forking code, but also to avoid forking
Hello,
As what we discussed in the yesterday’s meeting, the contradict is how to scale
out cascade services.
1) In PoC, one proxy node will only forward to one bottom openstack, the
proxy node will be added to a regarding AZ, and multiple proxy nodes for one
bottom OpenStack is feasible
Hi,
Why the permission of cinder.conf is set to 640 not 600? Can we set it to 600
instead of 640 and is there any problems if we change it?
Any input will be appreciate, thanks!
Wilson Liu
__
OpenStack Development Mailing
Btw, it's not a dependency conflict issue. If we install python
dependencies via pip, it's okay to be with foo=1.5.0 in the past, but not
now maybe (oslo.util - oslo_util breaks nearly everything). Maybe we need
a requirements.txt as release like:
foo==1.5.0
bar==2.1.0
not
for=1.5.0
bar=2.0.0
Hi folks,
As we discussed before, DAL needs to provide API to access resources in the
top and bottom OpenStack, so I implemented a client wrapper which has API
like this:
list_servers(self, cxt, site, fileters)
cxt is the context object storing authorization information, site tells DAL
where to
93 matches
Mail list logo
