Hi Phil,
2014/1/24 Day, Phil philip@hp.com
So I can see that option [1] would make the validation work by
(presumably) not including the shared network in the list of networks, but
looking further into the code allocate_for_instance() uses the same call to
decide which networks it
Hi,
I filed a bug [1] a while ago about the impact of a review [2] which now
prevents Nova to boot instances if there are two available networks
within Neutron.
As a side effect, users now need to pass the nic ID on the nova boot
command even for simple setups with only one private network
Le 23/01/2014 18:05, Day, Phil a écrit :
I think there is a cross-over point here somewhere - call it managed cloud
where the user doesn't want to run a cloud but does want (and is willing to pay for) some
guarantee of isolation of hypervisors, but also wants to share other aspects of the
Le 22/01/2014 02:50, Jay Pipes a écrit :
Yup, agreed. It's difficult to guess what the capacity implications
would be without having solid numbers on customer demands for this
functionality, including hard data on how long such instances would
typically live (see my previous point about
Le 22/01/2014 01:37, Dugger, Donald D a écrit :
Sylvain-
Tnx, that worked great.
(Now if I can just find a way to get the affinity tests working, all
the other tests pass. I only have 17 tests failing out of 254.)
I'm pretty busy these days with Climate 0.1 to deliver, but if I find
2014/1/22 Joe Gordon joe.gord...@gmail.com
On Tue, Jan 21, 2014 at 7:35 PM, Dugger, Donald D
donald.d.dug...@intel.com wrote:
Well, the first goal is to get the scheduler code into a separate tree,
even though that code is still utilizing common code from nova. Right now
just about
Hi Phil,
Le 21/01/2014 13:13, Day, Phil a écrit :
Hi Phil and Jay,
Phil, maybe you remember I discussed with you about the possibility of using
pclouds with Climate, but we finally ended up using Nova aggregates and a
dedicated filter.
That works pretty fine. We don't use instance_properties
Le 21/01/2014 12:57, Day, Phil a écrit :
So, I actually don't think the two concepts (reservations and
isolated instances) are competing ideas. Isolated instances are
actually not reserved. They are simply instances that have a
condition placed on their assignment to a particular compute node
Hi Don,
Look at how Climate is doing this [1]. The idea is to pull the master
tarball as an eggfile. That works fine, the only issues we have is when we
register opts to CONF where we could get DuplicateOpt if we try to register
opt with same name when importing.
-Sylvain
[1] :
Le 20/01/2014 16:57, Jay Pipes a écrit :
On Mon, Jan 20, 2014 at 10:18 AM, Day, Phil philip@hp.com
mailto:philip@hp.com wrote:
HI Folks,
The original (and fairly simple) driver behind
whole-host-allocation
(https://wiki.openstack.org/wiki/WholeHostAllocation) was to
Hi Jay,
Le 20/01/2014 17:34, Jay Pipes a écrit :
On Mon, Jan 20, 2014 at 11:18 AM, Sylvain Bauza
sylvain.ba...@bull.net mailto:sylvain.ba...@bull.net wrote:
Jay, please be aware of the existence of Climate, which is a
Stackforge project for managing dedicated resources (like AWS
2014/1/20 Jay Pipes jaypi...@gmail.com
But I believe that the two concerns can be tackled separately.
Indeed. I fully agree with the fact isolation can be provided by Nova, and
Climate would by the way happy to leverage it for providing capacity
planning on top of it.
By the way, I'm
Le 16/01/2014 17:18, Vishvananda Ishaya a écrit :
On Jan 16, 2014, at 6:46 AM, Joe Gordon joe.gord...@gmail.com
mailto:joe.gord...@gmail.com wrote:
On Wed, Jan 15, 2014 at 1:29 PM, Dugger, Donald D
donald.d.dug...@intel.com mailto:donald.d.dug...@intel.com wrote:
My thought was to
Hi Doug,
Count me in. Climate is currently working on delivering its first
python-climateclient but it would be great if we could leverage any olso
lib for this.
-Sylvain
2014/1/15 Doug Hellmann doug.hellm...@dreamhost.com
Several people have mentioned to me that they are interested in, or
:)
On Mon, Jan 13, 2014 at 6:58 PM, Sergey Lukjanov
slukja...@mirantis.comwrote:
Are there any guys from PST timezone?
On Mon, Jan 13, 2014 at 5:32 PM, Sylvain Bauza
sylvain.ba...@gmail.comwrote:
I can propose anytime at 0600 UTC, I can make efforts for waking up
earlier
One more thing, we can meet up on #openstack-climate (logging available),
or we can take a room in #openstack-meeting for starting a formal meeting
and get minutes.
Both are convenient for me, but with a preference for #openstack-climate.
-Sylvain
2014/1/14 Sylvain Bauza sylvain.ba
Hi team,
As agreed during our last meeting, we need to discuss on the progression
before code freeze next Tuesday.
I could propose tomorrow Wed 15 1000 UTC on #openstack-climate.
+1/-1 to this, please.
-Sylvain
___
OpenStack-dev mailing list
Thanks Don for raising the point, I was about to send an email after
finishing up to review.
To me, it appears I have to give -1 when either :
1. Change is related to API documentation or WSGI framework. AIUI, Gantt
will be plugged to Nova thanks to its RPC interface, it makes no sense to
ship
Le 27/12/2013 10:24, Nikolay Starodubtsev a écrit :
Hi all,
Guys, I want to say that keystoneclient package on pypi is too old.
For example it hadn't Client func in keystoneclient/client.py. May be
someone can help me with this?
Speaking of python-keystoneclient, the latest release is
Le 13/01/2014 13:49, Thierry Carrez a écrit :
Sylvain Bauza wrote:
Le 27/12/2013 10:24, Nikolay Starodubtsev a écrit :
Hi all,
Guys, I want to say that keystoneclient package on pypi is too old.
For example it hadn't Client func in keystoneclient/client.py. May be
someone can help me
I can propose anytime at 0600 UTC, I can make efforts for waking up earlier
:-)
I can yet understand that other EU people couldn't attend the call, so I
will aggregate and feedback all the topics for my French peers.
-Sylvain
2014/1/13 Nikolay Starodubtsev nstarodubt...@mirantis.com
Hi, all!
Le 13/01/2014 15:00, Dolph Mathews a écrit :
Ooh, I meant to get this done last week as I agree that keystoneclient
needed to see a new release, but it totally slipped my mind.
python-keystoneclient 0.4.2 is now available on pypi!
https://pypi.python.org/pypi/python-keystoneclient/0.4.2
I think we should still review the patches in case of any merging issues
with Gantt code. If the volume of reviews is high, then we have to increase
the number of reviewers.
I was part of the discussions for an external scheduler, I will dedicate
some time for +1...
Afaik, the current weekly
Hi folks,
Please keep in mind that our weekly meeting changed its timeslot from
Mondays to Fridays 1500 UTC.
#openstack-meeting should be available at this time, booking it.
-Sylvain
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Kudos to Dina for the PTL position. 3 vs. 5 with 80% participation means
it's a good thing for Climate : this is not a Stackforge project pushed by
only one sponsor and having a benevolent dictator, but rather a mix of
various experiences and subprojects with people having various ideas.
Now,
will not be available for this period?
Currently, we have 70% participation (poll have been started 18h ago).
On Thu, Dec 26, 2013 at 2:27 AM, Sylvain Bauza sylvain.ba...@gmail.comwrote:
Hi. I know that's pretty late for asking but could we consider having a
quorum for voting ?
As the election
Hi Ulrich,
I already discussed with Tim during last Swiss meetup at CERN about how
Climate could maybe help you on your use cases. There are still many things
to discuss and a demo to run out so we could see if it match your needs.
Basically, Climate is a new Stackforge project planning to
Hi. I know that's pretty late for asking but could we consider having a
quorum for voting ?
As the election is running during vacations for most of the team, my
concern is to make sure there are enough voters.
Thanks,
Sylvain
Le 25 déc. 2013 11:08, Sergey Lukjanov slukja...@mirantis.com a écrit
. Or
we can move to 1900-2000UTC. it looks fine for me. Or move to early
Europe morning.
*__*
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
2013/12/19 Sylvain Bauza sylvain.ba...@bull.net
mailto:sylvain.ba...@bull.net
Le 19/12/2013 13:57, Dina Belova
for Fridays 1500 UTC
On Fri, Dec 20, 2013 at 1:26 PM, Sylvain Bauza
sylvain.ba...@bull.net mailto:sylvain.ba...@bull.net wrote:
Well, 2000UTC means midnight for you, guys. Not really
safe for family concerns :-)
Maybe you were meaning 2000
Le 18/12/2013 16:37, Steven Dake a écrit :
In the early days of incubation requests, I got the distinct
impression managers at companies believed that actually getting a
project incubated in OpenStack was not possible, even though it was
sparsely documented as an option. Maybe things are
Hi team,
I won't be able to attend the next two weekly meetings (23Dec and
30Dec), I would like to postpone our meetings till 6th January 2014.
Any objections to this ?
-Sylvain
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Le 19/12/2013 13:54, Sergey Lukjanov a écrit :
yup, agreed. Additionally, I'd like to start a discussion about new
meeting time that'd be more US-folks friendly.
Luckily, we do have Internet now :
Le 19/12/2013 13:57, Dina Belova a écrit :
I have Christmas holidays till 12th January... So I don't really know
I if I will be available 6th Jan.
Oh ok. Who else are still on vacation these times ?
We can do our next meeting on 12th Jan, but I'm concerned with the
delivery of Climate 0.1
Hi,
I hereby would like to announce my candidacy for the Climate
(Reservations) PTL.
A brief history about me : I'm playing with Software Engineering and
Operations since more than 10 years, with a special focus on Openstack
since the Essex release. I promoted Openstack in my previous
Le 17/12/2013 14:59, Thierry Carrez a écrit :
Mark McLoughlin wrote:
On Tue, 2013-12-17 at 13:44 +0100, Thierry Carrez wrote:
Mark McLoughlin wrote:
How about if we had an emerging projects page where the TC feedback on
each project would be listed?
That would give visibility to our
Le 18/12/2013 11:25, Thierry Carrez a écrit :
Sylvain Bauza wrote:
Well, correct me if I'm wrong, but Stackforge is already the place for
promising projects ? If so, why creating a wikipage for listing them ?
Not really. Any project can be in stackforge. It doesn't have to be
promising
Le 18/12/2013 11:40, Thierry Carrez a écrit :
I guess there are 3 options:
1. Require diversity for incubation, but find ways to bless or recommend
projects pre-incubation so that this diversity can actually be achieved
2. Do not require diversity for incubation, but require it for
graduation,
Le 16/12/2013 10:41, Dina Belova a écrit :
Hello!
Guys, I have no opportunity to hold our IRC meeting today. I propose
to move it tomorrow, the same time.
Please let me know if you are OK with that.
Thank you!
+2 to this.
No regular meetings planned on Tuesdays 1000UTC as per
Hi Kevin,
2013/12/2 Fox, Kevin M kevin@pnnl.gov
Hi all,
I just want to run a crazy idea up the flag pole. TripleO has the concept
of an under and over cloud. In starting to experiment with Docker, I see a
pattern start to emerge.
* As a User, I may want to allocate a BareMetal node
While I agree with most of what Thierry said, I need clarifications though,
on what a Program is, and what is the key point where an idea should get
its own Program instead of being headed by an already existing Program.
For example, take Barbican which is providing extra features to Keystone,
or
thie...@openstack.org
Sylvain Bauza wrote:
While I agree with most of what Thierry said, I need clarifications
though, on what a Program is,
A team is a group of people working on a given mission. They can be
freely created. They apply to become an OpenStack Program if they feel
their (well
Apologies for the miss, I just double-checked and Nova does have its own
mission statement :
http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml
Thanks,
-Sylvain
2013/12/13 Sylvain Bauza sylvain.ba...@gmail.com
Thanks Thierry.
AFAIK, Compute (Nova) is not having
the process, which should make
things easy to implement and scale.
Thanks,
Kevin
From: Sylvain Bauza [sylvain.ba...@gmail.com]
Sent: Thursday, December 12, 2013 11:43 PM
To: OpenStack Development Mailing List, (not for usage questions)
Subject: Re
, 2013, Sylvain Bauza wrote:
Well, I wouldn't say more, I also have family concerns ;-)
I will prepare the meeting by checking all individual actions, so I will
only raise the left ones.
Hooks clarification can be postponed to the next meeting or discussed
directly on chan.
I saw you made
Huge thanks for our Russian peers who did exceptional efforts for joining
us exceptionnally today at 2000 UTC (midnight their time), I owe you a beer
:-)
You can find our weekly meeting minutes on
http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-09-20.01.html
Thanks,
-Sylvain
blueprints for 0.1. Some are
good, some need to be discussed, IMHO. For example, not having policies
in Climate sounds a showstopper to me.
-Sylvain
Le 09/12/2013 10:38, Dina Belova a écrit :
I think it's ok, but not more than a half of hour
On Monday, December 9, 2013, Sylvain Bauza wrote
Le 05/12/2013 11:03, Matthew Booth a écrit :
On Thu, 2013-12-05 at 11:35 +0200, Roman Prykhodchenko wrote:
Hi folks,
Open Stack community grows continuously bringing more people and so new
initiatives and new projects. This growing amount of people, initiatives
and projects causes increasing
Le 04/12/2013 06:01, John Wood a écrit :
I was curious if there is an OpenStack project that would be a good example to
follow as we convert Barbican over to oslo messaging.
I've been examining existing OpenStack projects such as Ceilometer and Keystone
to see how they are utilizing oslo
Great tool !
Just discovered that openstack.common.rpc does have typos, another good
reason to migrate to oslo.messaging.rpc :-)
-Sylvain
2013/12/3 Joe Gordon joe.gord...@gmail.com
HI all,
Recently I have seen a few patches fixing a few typos. I would like to
point out a really nifty tool
Le 02/12/2013 18:12, Russell Bryant a écrit :
On 12/02/2013 10:59 AM, Gary Kotton wrote:
I think that this is certainly different. It is something that we we want
and need a user facing API.
Examples:
- aggregates
- per host scheduling
- instance groups
Etc.
That is just taking the nova
Hi Jarret,
2013/12/2 Jarret Raim jarret.r...@rackspace.com
It's also pretty easy for a stackforge project to opt-in to the global
requirements sync job now too.
Are there some docs on how to do this somewhere? I added a task for us to
complete the work as part of the incubation request
Le 28/11/2013 17:04, Chris Friesen a écrit :
On 11/28/2013 09:50 AM, Gary Kotton wrote:
One option worth thinking about is to introduce a new scheduling
driver to
nova - this driver will interface with the external scheduler. This will
let us define the scheduling API, model etc, without
Indeed, Climate is also impacted.
Is there a bug already open or shall I create one ?
-Sylvain
Le 26/11/2013 10:46, Chmouel Boudjnah a écrit :
On Tue, Nov 26, 2013 at 9:52 AM, Flavio Percoco fla...@redhat.com
mailto:fla...@redhat.com wrote:
This seems to be the issue you're talking
Created https://bugs.launchpad.net/openstack-ci/+bug/1255041
Le 26/11/2013 11:34, Sylvain Bauza a écrit :
http://zuul.openstack.org/rechecks is not mentioning it by the way.
Le 26/11/2013 11:32, Sylvain Bauza a écrit :
Indeed, Climate is also impacted.
Is there a bug already open or shall I
As said earlier, I also would love to join the team, triggering a few
blueprints or so.
By the way, I'm currently reviewing the Scheduler code. Do you began to
design the API queries or do you need help for that ?
-Sylvain
Le 25/11/2013 08:24, Haefliger, Juerg a écrit :
Hi Robert,
I see
Hi,
You can find our today's meeting minutes here :
http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-11-25-09.59.html
Thanks,
-Sylvain
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hi,
Declaring Exceptions in Openstack projects is quite straightforward and
identical for most of the projects : all of them are defined in a global
exception.py module called each time a specific exception must be handled.
I recently received a -1 for that, so I would like to come back to
De : Robert Collins [robe...@robertcollins.net]
Date d'envoi : jeudi 21 novembre 2013 21:58
À : OpenStack Development Mailing List
Objet : [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest
proposal for an external scheduler in our
Hi Yuriy, Dolph et al.
I'm implementing a climate.policy.check_is_admin(ctx) which will look at
policy.json entry 'context_is_admin' for knowing which roles do have
elevated rights for Climate.
This check must be called when creating a context for knowing if we can
allow extra rights. The
Le 21/11/2013 10:04, Yuriy Taraday a écrit :
On Thu, Nov 21, 2013 at 12:37 PM, Sylvain Bauza
sylvain.ba...@bull.net mailto:sylvain.ba...@bull.net wrote:
Hi Yuriy, Dolph et al.
I'm implementing a climate.policy.check_is_admin(ctx) which will
look at policy.json entry
Hi,
When reviewing https://review.openstack.org/#/c/54539/, it appeared to
me that we need to make consensus on the way to know that a request is
having admin creds.
Currently, for implementing policies check in Climate, I'm looking at
context.roles dict, which contains the unicode string
Le 20/11/2013 11:18, Julien Danjou a écrit :
It depends on how fine grained you want your ACL to be,
Then, that's policy matter to let you know if you can trust the user or not.
I'm digging into
http://adam.younglogic.com/2013/11/policy-enforcement-in-openstack/,great value
for knowing how
Hi Yuriy,
Le 20/11/2013 11:56, Yuriy Taraday a écrit :
Looking at implementations in Keystone and Nova, I found the only use
for is_admin but it is essential.
Whenever in code you need to run a piece of code with admin
privileges, you can create a new context with is_admin=True keeping
all
to have is_admin
param to use.
On Wed, Nov 20, 2013 at 3:21 PM, Sylvain Bauza sylvain.ba...@bull.net
mailto:sylvain.ba...@bull.net wrote:
Hi Yuriy,
Le 20/11/2013 11:56, Yuriy Taraday a écrit :
Looking at implementations in Keystone and Nova, I found the only
use for is_admin
Le 14/11/2013 20:46, Clint Byrum a écrit :
Now, choose which city will grow faster and produce more innovation.
The problem is larger than only innovation, it is also making sure the
Stackforge projects are also a starting point for contributing to
Openstack in a different manner. ATCs can
Hi all,
I'm trying to implement policy rules for Climate API, making sure some
endpoints need admin rights, and looked at how it's managed on other
Openstack projects like Nova.
There is huge discrepancy in between openstack.common.policy files from
Nova and Cinder and the latest
Le 15/11/2013 11:20, Julien Danjou a écrit :
On Fri, Nov 15 2013, Sylvain Bauza wrote:
Any help from Oslo mainteners ? Any doc in there ?
You want to use the latest version from oslo-incubator, for sure.
I think Ceilometer is good starting example as how to use it, as our
policy usage
Hi,
As previously agreed, regular weekly IRC meeting will take place today
at 1000 UTC exceptionnally.
We'll switch back to Mondays 1000 UTC starting next week.
Save the date, don't forget it.
Thanks,
-Sylvain
___
OpenStack-dev mailing list
Thanks all for your presence.
Please find the logs of the meeting here :
http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-11-13-09.59.html
Next meeting will be held Monday 18th Nov 1000 UTC.
Cheers,
-Sylvain
Le 13/11/2013 10:11, Sylvain Bauza a écrit :
Hi,
As previously
Hi,
During the Design session
https://etherpad.openstack.org/p/NovaIcehouse-Instance-Group-API we discussed
the fact that this is not the role of Nova for doing atomic reservations in
order to ensure the user needs will be met.
I raised the point (and sorry for my bad accent, was stressy)
De : Sylvain Bauza [sylvain.ba...@bull.net]
Date d'envoi : mercredi 6 novembre 2013 10:47
À : openstack-dev@lists.openstack.org
Objet : [openstack-dev] [Nova] [Climate] Reservation service called Climate
Hi,
During the Design session
https://etherpad.openstack.org/p/NovaIcehouse
Hi Climate folks,
Mondays 1000 UTC is the regular timeslot for Climate IRC weekly
meetings, but there will be some impacts for the next 2 weeks :
- Monday 4/11, we all will be flying to the Openstack Summit, either
already in HK or on track.
- Monday 11/11 is a day off in France
Here is
...@mirantis.com
mailto:dbel...@mirantis.com wrote:
I'm OK with 1/, but I have flight from HK exactly 12/11, that's
why 2/ is not really comfortable for me.
Dina
On Wed, Oct 30, 2013 at 2:53 PM, Sylvain Bauza
sylvain.ba...@bull.net mailto:sylvain.ba...@bull.net wrote:
Hi
Le 30/10/2013 14:41, Dina Belova a écrit :
Hi everyone!
I've added Climate into the 'openstack' group on Launchpad to make
Gerrit links to BPs working. Additionally I've updated project
description to cover current status.
Cool ! Nice to see you found the root cause for the broken links
I had the same concern, and only ended up exporting my Sched.org agendas
(the sessions I starred) to my own Google agenda (using iCal) in order
to see the conflicts.
Hope it can helps,
-Sylvain
Le 29/10/2013 04:08, Lu, Lianhao a écrit :
Hi all,
Looks like we have
Hi all,
Climate is growing and time is coming for having a weekly meeting in
between all of us.
There is a huge number of reviews in progress, and at least the first
agenda will be triaging those, making sure they are either coming to
trunk as soon as possible, or splitted into smaller chunks
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
On Thu, Oct 24, 2013 at 4:11 PM, Swann Croiset
swann.croi...@bull.net mailto:swann.croi...@bull.net wrote:
+1
Le 24/10/2013 09:45, Sylvain Bauza a écrit :
Hi all,
Climate is growing and time
Long-story short, sounds like we do have the same concerns here in Climate.
I'll be present at the Summit, any chance to do an unconference meeting
in between all parties ?
Thanks,
-Sylvain
Le 11/10/2013 08:25, Mike Spreitzer a écrit :
Regarding Alex's question of which component does
,
Yathi.
From: Sylvain Bauza sylvain.ba...@bull.net
mailto:sylvain.ba...@bull.net
Date: Tuesday, October 8, 2013 12:40 AM
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
mailto:openstack-dev@lists.openstack.org
Cc: Yathiraj Udupi yud...@cisco.com mailto:yud...@cisco.com
Hi Yathi,
Le 08/10/2013 05:10, Yathiraj Udupi (yudupi) a écrit :
Hi,
Based on the discussions we have had in the past few scheduler
sub-team meetings, I am sharing a document that proposes an
updated Instance Group Model and API extension model.
This is a work-in-progress draft version, but
Hi Mike,
Dina and you outlined some differences in terms of seeing what is
dependent on what.
As Dina explained, Climate plans to be integrated into Nova and Heat
logics, where Heat and Nova would request Climate API by asking for a
lease and would tag on their own the resources as
Hi team,
So far as I can see, the current way for unittest the DB APIs in Openstack is
either mocking the DB or using a tmp/ram sqlite engine.
I went through Fixture SQLAlchemy DataSets [1], I would give a try on it.
Anyone shouting no ?
Maybe other Openstack folks could shed some light on the
Hi Mike and Zane,
Le 27/09/2013 15:58, Mike Spreitzer a écrit :
Zane Bitter zbit...@redhat.com wrote on 09/27/2013 08:24:49 AM:
Your diagrams clearly show scheduling happening in a separate stage to
(infrastructure) orchestration, which is to say that at the point where
resources are
questions, here to help!
-Josh
From: Sylvain Bauza sylvain.ba...@bull.net
mailto:sylvain.ba...@bull.net
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
mailto:openstack-dev@lists.openstack.org
Date: Monday, September 23, 2013 12:20 AM
To: OpenStack Development
or not.
On Thu, Sep 19, 2013 at 4:54 PM, Sylvain Bauza sylvain.ba...@bull.net
mailto:sylvain.ba...@bull.net wrote:
Hi Climate team,
I just went through https://wiki.openstack.org/wiki/TaskFlow
Do you think Taskflow could help us in providing ressources
defined in the lease on an atomic
Hi Climate team,
I just went through https://wiki.openstack.org/wiki/TaskFlow
Do you think Taskflow could help us in providing ressources defined in
the lease on an atomic way ?
We could leave the implementation up to the plugins, but maybe the Lease
Manager could also benefit of it.
Hi Jake,
Come in #openstack-ironic, I'll try to help you as much as I can. I
tested the latest baremetal driver using devstack and real baremetal
hosts (using IPMI), it works like a charm.
Btw, I'm planning to write a blogpost about how to devstack using
baremetal driver. Hope it will help
Hi Murali,
Le 02/09/2013 15:19, Murali Balcha a écrit :
I am not an expert in Heat but the way I understood the Heat project is that it
is an orchestration layer that instantiate a composite application based on a
template definition. The template may identify the vms, networks and storage
Please note that there is huge improvement in terms of perfs if you
choose to cherry-pick the libgfapi driver which has recently been
implemented in Nova [1].
That would assume you use Cinder bootable volumes instead of classical
QCOW2 instances, but the improvement is worth it.
-Sylvain
#For_which_distributions_does_RDO_provide_packages.3F
* This means we can just include the RDO repo rpm (like epel and
use that openvswitch version there) instead of build your own.
Hope some of this offers some good pointers.
-Josh
From: Sylvain Bauza sylvain.ba...@bull.net
mailto:sylvain.ba...@bull.net
Date: Tuesday
Cross-posting to openstack-ops@.
Maybe someone experienced the same issue and workarounded it ?
-Sylvain
Le 12/08/2013 18:10, Sylvain Bauza a écrit :
Hi,
./smithy -a install -p conf/personas/in-a-box/basic-neutron.yaml is
failing because of openvswitch missing.
See logs here [1].
Does
Hi,
./smithy -a install -p conf/personas/in-a-box/basic-neutron.yaml is
failing because of openvswitch missing.
See logs here [1].
Does anyone knows why openvswitch is needed when asking for linuxbridge
in components/neutron.yaml ?
Shall I update distros/rhel.yaml ?
-Sylvain
[1] :
501 - 593 of 593 matches
Mail list logo
