On 10/19/2014 09:33 AM, Avishay Traeger wrote:
Hi Preston,
Replies to some of your cinder-related questions:
1. Creating a snapshot isn't usually an I/O intensive operation. Are
you seeing I/O spike or CPU? If you're seeing CPU load, I've seen the
CPU usage of cinder-api spike sometimes - not
-Original Message-
From: Christopher Aedo [mailto:d...@aedo.net]
Sent: 21 October 2014 04:45
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [All] Maintenance mode in OpenStack during
patching/upgrades
...
Also, I would like to see
Running integration_test from command line is ok :
(.venv)whg@whg-HP:/opt/stack/horizon$ nosetests
openstack_dashboard.test.integration_tests.tests.test_user_settings
openstack_dashboard.test.integration_tests.tests.test_user_settings.TestUserSettings.test_user_settings_change
... ok
Thanks for the pointer!
I like how the first google hit for this is:
Add details on dhcp_agents_per_network option for DHCP agent HA
https://bugs.launchpad.net/openstack-manuals/+bug/1370934
:) Seems reasonable to set dhcp_agents_per_network 1. What happens when
a DHCP agent dies? Does the
Hi Kevin,
The current method outlined in [1] is to manually assign networks to dhcp
agents. I need to be able to kill the node running the dhcp agent and
start it up on another node without manual intervention. Someone else
pointed me to the dhcp_agents_per_network option which I'm looking into
On Mon, Oct 20, 2014 at 10:19 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Sat, Oct 18, 2014 at 10:04 AM, Roman Bogorodskiy
rbogorods...@mirantis.com wrote:
Hi,
In discussion of this spec proposal:
https://review.openstack.org/#/c/127827/ it was suggested by Joe Gordon
to start a
I am trying to find a way of creating a dynamic List of
Resources(Loadbalancer PoolMembers to be exact) using Heat.
The idea is that the number of PoolMembers and the required Addresses would
be received as Heat parameters.
However, I am unable to get %index% working inside a Fn:Select block.
No, unfortunately when the DHCP agent dies there isn't automatic
rescheduling at the moment.
On Mon, Oct 20, 2014 at 11:56 PM, Noel Burton-Krahn n...@pistoncloud.com
wrote:
Thanks for the pointer!
I like how the first google hit for this is:
Add details on dhcp_agents_per_network option for
I would say that wipe-on-delete is not necessary in most deployments.
Most storage backends exhibit the following behavior:
1. Delete volume A that has data on physical sectors 1-10
2. Create new volume B
3. Read from volume B before writing, which happens to map to physical
sector 5 - backend
On 10/21/2014 02:11 AM, Devananda van der Veen wrote:
Hi all,
I was reminded in the Ironic meeting today that the words hardware
discovery are overloaded and used in different ways by different
people. Since this is something we are going to talk about at the
summit (again), I'd like to start
Hello hello!
I'm trying to bring up a solum development environment with vagrant
devstack, but I'm having problems running any of the example assemblys.
They all get suck at status BUILDING like follows:
vagrant@devstack:/var/log/solum/worker$ solum assembly show
Le 20 oct. 2014 20:13, Dan Smith d...@danplanet.com a écrit :
OK, so in reviewing Dan B's patch series that refactors the virt
driver's get_available_resource() method [1], I am stuck between two
concerns. I like (love even) much of the refactoring work involved in
Dan's patches. They
On 10/20/2014 08:00 PM, Andrew Laski wrote:
One of the big goals for the Kilo cycle by users and developers of the
cells functionality within Nova is to get it to a point where it can be
considered a first class citizen of Nova. Ultimately I think this comes
down to getting it tested by
On Mon, Oct 20, 2014 at 03:27:19PM -0700, Joe Gordon wrote:
On Mon, Oct 20, 2014 at 11:12 AM, gordon chung g...@live.ca wrote:
The issue I'm highlighting is that those projects using the code now
have
to update their api-paste.ini files to import from the new location,
+1 for the separation
I already gave up of the term discovery as you can see on the DRAC
Hardware Introspection[1] spec, I also don't think that
introspection is the best word for that (we already use the world
cloud for OpenStack so it can't get more confusing than that).
Perhaps interrogation
Sean Roberts wrote:
Chance we can move the congress session from Monday 14:30-16:00 to co-locate
Tuesday with GBP? either before or after...
Let me ask Chris Hoge (who is in charge of the larger ecosystem
sessions), see if you could switch from Monday to Tuesday.
--
Thierry Carrez (ttx)
I agree with Devananda's definition of Œhardware discovery¹ and other
tools similar to Ironic use the term discovery in this way, however I have
found that these other tools often bundle the gathering of the system
properties together with the discovery of the hardware as a single step
from a user
On 14/10/14 18:30, Aggarwal, Nikunj wrote:
Instead Horizon guys came to an conclusion that we will identify the
browser type and version to deal with legacy browsers like older IE
or firefox or any other browser and for other major features we can
use feature detection with Modernizr.
I
On Tue, Oct 21, 2014 at 10:27 AM, Sam Betts (sambetts)
sambe...@cisco.com wrote:
I agree with Devananda's definition of Œhardware discovery¹ and other
tools similar to Ironic use the term discovery in this way, however I have
found that these other tools often bundle the gathering of the system
On 10/20/2014 07:38 PM, Jay Pipes wrote:
Hi Dan, Dan, Nikola, all Nova devs,
OK, so in reviewing Dan B's patch series that refactors the virt
driver's get_available_resource() method [1], I am stuck between two
concerns. I like (love even) much of the refactoring work involved in
Dan's
On Mon, Oct 20, 2014 at 03:27:19PM -0700, Joe Gordon wrote:
On Mon, Oct 20, 2014 at 11:12 AM, gordon chung g...@live.ca wrote:
The issue I'm highlighting is that those projects using the code now
have
to update their api-paste.ini files to import from the new location,
On 10/20/2014 04:34 PM, Ben Nemec wrote:
I guess my only concern would be whether either of those things are
contentious (both sound like must-do's at some point) and whether there
is anything on either topic that requires f2f conversation to resolve.
There's a spec out for Cinder HA already
Which Linux distribution are you using? The BUILDING state ends when an AQMP
message is seen by Solum from the Solum worker process. If the queue is not
working, then the states will not change. There is at least one version of
Ubuntu that produced a nonfunctional queue setup before. I suggest
Hi,
Sorry for the top posting but it was hard to fit my complete view inline.
I'm also thinking about a possible solution for automatic server evacuation. I
see two separate sub problems of this problem: 1)compute node monitoring and
fencing, 2)automatic server evacuation
Compute node
I was discussing $subject on #openstack-nova, Nikola Dipanov suggested
it's worthwhile to bring this up on the list.
I was looking at
http://kilodesignsummit.sched.org/
and noticed there's no specific session (correct me if I'm wrong) that's
targeted at coordination between OpenStack -
On Tue, Oct 21, 2014 at 12:58:48PM +0200, Kashyap Chamarthy wrote:
I was discussing $subject on #openstack-nova, Nikola Dipanov suggested
it's worthwhile to bring this up on the list.
I was looking at
http://kilodesignsummit.sched.org/
and noticed there's no specific session
-Original Message-
From: Daniel P. Berrange [mailto:berra...@redhat.com]
Sent: 21 October 2014 13:08
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Summit] Coordination between OpenStack
lower layer virt stack (libvirt, QEMU/KVM)
On
On 10/21/2014 06:44 AM, Balázs Gibizer wrote:
Hi,
Sorry for the top posting but it was hard to fit my complete view inline.
I'm also thinking about a possible solution for automatic server
evacuation. I see two separate sub problems of this problem:
1)compute node monitoring and fencing,
- Original Message -
From: Dolph Mathews dolph.math...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, October 20, 2014 4:38:25 PM
Subject: Re: [openstack-dev] Horizon and Keystone: API Versions and
- Original Message -
From: Ben Meyer ben.me...@rackspace.com
To: openstack-dev@lists.openstack.org
Sent: Monday, October 20, 2014 3:53:39 PM
Subject: Re: [openstack-dev] [Keystone] Question regarding Service Catalog
andIdentity entries...
On 10/20/2014 08:12 AM, Jamie
-Original Message-
From: Russell Bryant [mailto:rbry...@redhat.com]
Sent: October 21, 2014 15:07
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Automatic evacuate
On 10/21/2014 06:44 AM, Balázs Gibizer wrote:
Hi,
Sorry for the top posting but it was
On Tue, Oct 21, 2014 at 8:34 AM, Jamie Lennox jamielen...@redhat.com
wrote:
The only reason is that I didn't want to introduce a global variable cache
in a library. The session should be a fairly long running object and i'm
looking at ways we could serialize it to allow horizon/CLIs to manage
Hi,
I have a lot of documentation around DevStack and some configurations
that I run for a multi-node lab, that uses Neutron and IPv6. I would
love to contribute to them, but they are currently in Markdown format.
Looking at the current docs, they are all currently in raw HTML, and I
was hoping
Hello,
I would like to add to DevStack the ability to stand up Nova with LVM
ephemeral
storage. Below is a draft of the blueprint describing the proposed feature.
Suggestions on architecture, implementation and the blueprint in general
are very
welcome.
Best,
Dan
Hi,
As for a separate section for plugins, I think we should not force it and
leave this decision to a plugin developer, so he can create just a single
checkbox or a section of the settings tab or a separate tab depending on
plugin functionality. Plugins should be able to modify arbitrary release
Hi,
to help the discussion,
a small compilation about the bugs and previous attempts to fix the
missing functionality in cells.
Aggregates
https://bugs.launchpad.net/nova/+bug/1161208
https://blueprints.launchpad.net/nova/+spec/cells-aggregate-support
https://review.openstack.org/#/c/25813/
For LVM-thin I believe it is already disabled? It is only really
needed on LVM-thick, where the returning zeros behaviour is not done.
On 21 October 2014 08:29, Avishay Traeger avis...@stratoscale.com wrote:
I would say that wipe-on-delete is not necessary in most deployments.
Most storage
The Oslo team is pleased to announce the release of oslotest 1.2.0, our first
release for the Kilo cycle.
This release includes:
cfdb562 Updated from global requirements
118885e Set install_command in tox to avoid pre-releases
e5c14b7 Add an extra parameter for test directory in debugger script
On Tue, Oct 21, 2014 at 9:58 AM, Collins, Sean
sean_colli...@cable.comcast.com wrote:
Looking at the current docs, they are all currently in raw HTML, and I
was hoping that it would be possible to add Pelican[1], which would make
it easier to contribute documentation since we wouldn't have to
I do see mentions of gh-pages in the build_docs.sh script - is
devstack.org redirect to GitHub?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Oct 21, 2014 at 11:33:44AM EDT, Dean Troyer wrote:
On Tue, Oct 21, 2014 at 9:58 AM, Collins, Sean
sean_colli...@cable.comcast.com wrote:
Looking at the current docs, they are all currently in raw HTML, and I
was hoping that it would be possible to add Pelican[1], which would make
On Tue, Oct 21, 2014 at 11:52:26AM +, Tim Bell wrote:
It would also be interesting if the features of KVM could be made
available through OpenStack around the same time.. virtio-blk data
plane would be an example where we can't work out how to exploit it
out of the box under OpenStack.
As there are multiple interfaces using non versioned dicts and as we are
looking at reducing technical debt by Kilo, there are different
blueprints which can be worked in parallel.
I don't think I disagree with anything above, but I'm not sure what
you're getting at. I think the parallelism we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
introducing a new auxiliary feature (e.g. a new messaging backend;
some specific configuration of common services, like multiple workers
in neutron; a new db driver supported by oslo.db; a plugin that lacks
its own third-party CI like
Hi Kyle,
Can you pls. comment on this discussion and confirm the requirements for
getting out-of-tree mechanism_driver listed in the supported plugin/driver
list of the Openstack Neutron docs.
Thanks,
Vad
--
On Mon, Oct 20, 2014 at 12:48 PM, Anne Gentle a...@openstack.org wrote:
On Mon, Oct
use a OS::Neutron::PoolMember instead. Then each member template can add itself
to the pool.
From: Magesh GV [magesh...@oneconvergence.com]
Sent: Tuesday, October 21, 2014 12:07 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] Combination of Heat
On 10/21/2014 10:37 AM, Collins, Sean wrote:
I do see mentions of gh-pages in the build_docs.sh script - is
devstack.org redirect to GitHub?
Nope - it used to be. It's now built and published like the rest of
openstack docs.
Now - I don't want to get in the way of the work you're wanting to
Images that are premade and ready to go would be a huge step in the right
direction.
You currently are expected to make them all yourself, which involves a lot of
work/knowledge.
Its great to be able to build them, but right out of the gate, they are too
much work for a new user.
Thanks,
On Tue, Oct 21, 2014 at 11:59:12AM EDT, Monty Taylor wrote:
On 10/21/2014 10:37 AM, Collins, Sean wrote:
I do see mentions of gh-pages in the build_docs.sh script - is
devstack.org redirect to GitHub?
Nope - it used to be. It's now built and published like the rest of
openstack docs.
On Mon, Oct 20, 2014 at 01:38:46PM -0400, Jay Pipes wrote:
Hi Dan, Dan, Nikola, all Nova devs,
OK, so in reviewing Dan B's patch series that refactors the virt driver's
get_available_resource() method [1], I am stuck between two concerns. I like
(love even) much of the refactoring work
On Mon, Oct 20, 2014 at 11:12:57AM -0700, Dan Smith wrote:
OK, so in reviewing Dan B's patch series that refactors the virt
driver's get_available_resource() method [1], I am stuck between two
concerns. I like (love even) much of the refactoring work involved in
Dan's patches. They replace
On Tue, Oct 21, 2014 at 08:46:10AM -0700, Dan Smith wrote:
As there are multiple interfaces using non versioned dicts and as we are
looking at reducing technical debt by Kilo, there are different
blueprints which can be worked in parallel.
I don't think I disagree with anything above, but
On Tue, Oct 21, 2014 at 11:12 AM, Collins, Sean
sean_colli...@cable.comcast.com wrote:
On Tue, Oct 21, 2014 at 11:59:12AM EDT, Monty Taylor wrote:
On 10/21/2014 10:37 AM, Collins, Sean wrote:
I do see mentions of gh-pages in the build_docs.sh script - is
devstack.org redirect to GitHub?
Folks,
I'm canceling our weekly IRC meeting today since we've just released
Murano 2014.2 and still working on figuring out roadmap for Kilo
cycle.
Thanks,
Ruslan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
We currently have a mechanism for restarting the DHCP agent on another
node, but we'd like the new agent to take over all the old networks of the
failed dhcp instance. Right now, since dhcp agents are distinguished by
host, and the host has to match the host of the ovs agent, and the ovs
agent's
On 2014-10-21 10:59:12 -0500 (-0500), Monty Taylor wrote:
On 10/21/2014 10:37 AM, Collins, Sean wrote:
I do see mentions of gh-pages in the build_docs.sh script - is
devstack.org redirect to GitHub?
Nope - it used to be. It's now built and published like the rest of
openstack docs.
[...]
Excerpts from Adam Lawson's message of 2014-10-20 18:47:36 -0500:
I made a similar comment to the Triple-O design summmit etherpad in hopes
others have a similar interest in Kilo but I wanted to share evangelize my
thoughts with the community for discussion:
For better or for worse, one
Thx
~sean
On Oct 21, 2014, at 2:18 AM, Thierry Carrez thie...@openstack.org wrote:
Sean Roberts wrote:
Chance we can move the congress session from Monday 14:30-16:00 to co-locate
Tuesday with GBP? either before or after...
Let me ask Chris Hoge (who is in charge of the larger
Hi all -
Thanks for all the responses I got on my Make EngineFacade a Facade” spec -
plenty of people have commented, pretty much all positively so I’m pretty
confident we can start building the basic idea of that out into a new review.
I want to point out that there is another, closely
Having written/worked on a few DC automation tools, Ive typically broken
down the process of getting unknown hardware into production in to 4
distinct stages.
1) Discovery (The discovery of unknown hardware)
2) Normalising (Push initial configs like drac/imm/ilo settings, flashing
to known good
- Original Message -
-Original Message-
From: Russell Bryant [mailto:rbry...@redhat.com]
Sent: October 21, 2014 15:07
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Automatic evacuate
On 10/21/2014 06:44 AM, Balázs Gibizer wrote:
Hi,
Hi
We are in fact using OS::Neutron::PoolMember resource. I guess
ResourceGroup is the only iterative construct in Heat. Is the use case
supported today? I think this is more than a simple usage question, hence
posting it here. Thank you.
Regards
Subra
On Tue, Oct 21, 2014 at 8:55 AM, Fox,
I fully and wholeheartedly agree that inventory management is out of scope
of Ironic. But I have a small suggestion:
We'd do well as a community to adopt/evangelize an informal rule which I
enforce at work (because I see this happen a lot when brainstorming with
cross-project goals); we cannot
On 10/21/2014 07:53 PM, David Vossel wrote:
- Original Message -
-Original Message-
From: Russell Bryant [mailto:rbry...@redhat.com]
Sent: October 21, 2014 15:07
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Automatic evacuate
On 10/21/2014 06:44
- Original Message -
On Thu, Oct 16, 2014 at 7:48 PM, Jay Pipes jaypi...@gmail.com wrote:
While one of us (Jay or me) speaking for the other and saying we agree
is a distributed consensus problem that dwarfs the complexity of
Paxos
You've always had a way with words, Florian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Possible Glance image exposure via Swift
- ---
### Summary ###
Glance is able to use Swift as a back end for storing virtual machine
images. When Glance is configured this way (in multi-tenant mode only),
it is possible for unauthenticated users to
As a side-note, the new AWS flavors seem to indicate that the Amazon
infrastructure is moving to all ECS volumes (and all flash, possibly), both
ephemeral and not. This makes sense, as fewer code paths and less
interoperability complexity is a good thing.
That the same balance of concerns should
On Tue, Oct 21, 2014 at 11:26 AM, Adam Lawson alaw...@aqorn.com wrote:
I fully and wholeheartedly agree that inventory management is out of scope
of Ironic. But I have a small suggestion:
We'd do well as a community to adopt/evangelize an informal rule which I
enforce at work (because I see
On 10/21/2014 04:31 AM, Nikola Đipanov wrote:
On 10/20/2014 08:00 PM, Andrew Laski wrote:
One of the big goals for the Kilo cycle by users and developers of the
cells functionality within Nova is to get it to a point where it can be
considered a first class citizen of Nova. Ultimately I think
Sharing the vg with cinder is likely to cause some pain testing proposed
features cinder reconciling backend with the cinder db. Creating a second
vg sharing the same backend pv is easy and avoids all such problems.
Duncan Thomas
On Oct 21, 2014 4:07 PM, Dan Genin daniel.ge...@jhuapl.edu wrote:
Did you mean EBS? I thought it was generally hard to get the same kind
of performance from block storage that local ephemeral storage provides
but perhaps Amazon has found a way. Life would certainly be much simpler
with a single ephemeral backend. Storage pools
Do you mean that Cinder will be confused by Nova's volumes in its volume
group?
Yeah, sure that would be similarly easy to implement. Thank you for the
suggestion!
Dan
On 10/21/2014 03:10 PM, Duncan Thomas wrote:
Sharing the vg with cinder is likely to cause some pain testing
proposed
Yes, I meant EBS not ECS. Too many similar acronyms...
The thing about the Amazon folk is that they collect a lot of metrics, and
pretty much do everything on a fairly empirical basis. This is a huge
advantage. Starting thinking about what I could with good metrics and
building on the performance
On 21/10/14 14:05, Subrahmanyam Ongole wrote:
Hi
We are in fact using OS::Neutron::PoolMember resource. I guess
ResourceGroup is the only iterative construct in Heat. Is the use case
supported today? I think this is more than a simple usage question, hence
posting it here. Thank you.
Regards
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Configuring OpenStack deployments to prevent POODLE attacks
- ---
### Summary ###
POODLE (CVE-2014-3566) is a new attack on SSLv3 that allows an active
network-based attacker to recover the plaintext from a secure connection
using a CBC-mode cipher.
As far as I can tell when you specify:
dhcp_agents_per_network = X 1
The server binds the network to all the agents (up to X), which means that
you have multiple instances of dnsmasq serving dhcp requests at the same
time. If one agent dies, there is no fail-over needed per se, as the other
We've been iterating on Summit ideas on an etherpad [1] for the past
month or so now. Thanks to everyone for placing your ideas there! For
the past week, the Neutron drivers team has been taking a crack at
prioritizing these in preparation for the upcoming Summit. Based on
the priorities I've
Hi Armando,
Sort of... but what happens when the second one dies? If one DHCP agent
dies, I need to be able to start a new DHCP agent on another host and take
over from it. As far as I can tell right now, when one DHCP agent dies,
another doesn't take up the slack.
I have the same problem wit
So then it is probably best to leave existing Cinder LVM code in
lib/cinder_backends/lvm alone and create a similar set of lvm scripts
for Nova,
perhaps in lib/nova_backends/lvm?
Dan
On 10/21/2014 03:10 PM, Duncan Thomas wrote:
Sharing the vg with cinder is likely to cause some pain testing
The rationale behind two parallel data model hiercharies is that the
format the virt drivers report data in, is not likely to be exactly
the same as the format that the resoure tracker / scheduler wishes to
use in the database.
Yeah, and in cases where we know where that line is, it makes
- Original Message -
From: Steve Gordon sgor...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Hi all,
I took an action item in one of the meetings to try and find a
date/time/space to do another NFV BoF session for
Hi, Daniel's all,
This is a follow up to Daniel's
http://osdir.com/ml/openstack-dev/2014-10/msg00557.html , Info on XenAPI data
format for 'host_data' call.
I'm considering to change the compute capability to be a nova object,
with well defined field, the reasons are: a)
Ah, sorry. I misunderstood what you were trying to do.
Why create a template that takes in a list of pool members, rather then pass
the pool id to the template the instance is in, and use a PoolMember to attach
it?
Thanks,
Kevin
From: Subrahmanyam Ongole
David,
In the Horizon team meeting on the 14th[1], we had some discussion about where
we should host additional items like mockups that are associated with a
blueprint. Numerous suggestions came up but there wasn't any official clear
answer, so you said you'd check with the infra team. Were
Does rally provide any synchronization mechanism to synchronize between
multiple scenario, when running in parallel? Rally spawns multiple processes,
with each process running the scenario. We need a way to synchronize between
these to start a perf test operation at the same time.
regards,
Using the keystone client is currently quite painful for fuel. For
example getting tokens from a fuel env when auth required (which is
needed if we want to use curl or other clients) is currently quite a
mess.
In order to get a token you can
python EOF
from fuelclient.client import Client
Behzad,
Unfortunately at this point there is no support of locking between
scenarios.
It will be quite tricky for implementation, because we have different load
generators, and we will need to find
common solutions for all of them.
If you have any ideas about how to implement it in such way, I
Greetings all,
I'm using Heat from Icehouse and I'm hitting a problem that I'm hoping y'all
can shed some light on.
I have no problems doing stack-create. I can watch the MySQL commands go by and
see it happily update the stack table so that it eventually shows up as
CREATE_COMPLETE. When I
On Tue, Oct 21, 2014 at 12:32 PM, Zane Bitter zbit...@redhat.com wrote:
On 21/10/14 14:05, Subrahmanyam Ongole wrote:
Hi
We are in fact using OS::Neutron::PoolMember resource. I guess
ResourceGroup is the only iterative construct in Heat. Is the use case
supported today? I think this is
On Tue, Oct 21, 2014 at 4:43 PM, Hemanth Ravi hemanthrav...@gmail.com
wrote:
On Tue, Oct 21, 2014 at 12:32 PM, Zane Bitter zbit...@redhat.com wrote:
On 21/10/14 14:05, Subrahmanyam Ongole wrote:
Hi
We are in fact using OS::Neutron::PoolMember resource. I guess
ResourceGroup is the only
Hi all,
On the cross project meeting today, i promised to bring this to the
ML[1]. So here it is:
Question : Can a StackForge project (like nova-docker), depend on a
library (docker-py) that is not specified in global requirements?
Right now the answer seems to be No, as enforced by the CI
We merged caching support for the metadata agent in juno, and backported to
icehouse. It was enabled by default in juno, but disabled by default in
icehouse to satisfy the stable maint requirement of not changing functional
behavior.
While performance of the agent was improved with caching
On Tue, Oct 21, 2014 at 08:09:38PM -0400, Davanum Srinivas wrote:
Hi all,
On the cross project meeting today, i promised to bring this to the
ML[1]. So here it is:
Question : Can a StackForge project (like nova-docker), depend on a
library (docker-py) that is not specified in global
Hi,
I would like to propose the requirement of 2 reviewers (at least one of them
being Glance core), for a spec in order to be approved.
This proposal is a step to better plan the development work and help the team
prioritize on the reviews and features. The anticipation is that it will help
- Original Message -
From: Andrew Laski andrew.la...@rackspace.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
One of the big goals for the Kilo cycle by users and developers of the
cells functionality within Nova is to get it
Hi,
Many thanks to Steve to link these topics together.
+1
Consider that there are lots of production installation of cells solution, the
improvement on cells are definitely necessary.
And also hope to add the following demand for the large cloud operator (
especially cloud for NFV ) in the
It sounds like the only reasonable option we are left with right now is to
document.
Even if we enabled/removed the backport, it would take time until users can
get their hands on a new cut of the stable branch.
We would need to be more diligent in the future and limit backports to just
bug
On 22/10/14 03:07, Andrew Laski wrote:
On 10/21/2014 04:31 AM, Nikola Đipanov wrote:
On 10/20/2014 08:00 PM, Andrew Laski wrote:
One of the big goals for the Kilo cycle by users and developers of the
cells functionality within Nova is to get it to a point where it can be
considered a first
Thanks for this.
It would be interesting to see how much of this work you think is
achievable in Kilo. How long do you see this process taking? In line
with that, is it just you currently working on this? Would calling for
volunteers to help be meaningful?
Michael
On Tue, Oct 21, 2014 at 5:00
Hi, all
I’m trying to connect ofagent to switches other than OVS.
But, it’s not going. I think that the ofagent cannot connect their switches.
Is there anyone tried?
Hirofumi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
1 - 100 of 102 matches
Mail list logo
