On Oct 16, 2013, at 08:45 , Vishvananda Ishaya
wrote:
> Hi Sean,
>
> I'm going to top post because my response is general. I totally agree that we
> need people that understand the code base and we should encourage new people
> to be cross-functional. I guess my main issue is with how we ge
On Wed, Oct 16, 2013 at 12:40 AM, Mathew R Odden wrote:
> As requested in the last Oslo meeting, I created a blueprint for further
> discussion on the i18n work in Icehouse here:
>
> https://blueprints.launchpad.net/oslo/+spec/i18n-messages
>
> There were some ideas from the meeting that I'm sure
On 16/10/13 03:22, Robert Collins wrote:
> Hi, during the TripleO meeting today we had two distinct discussions
> about reviews.
>
> Firstly, our stats have been slipping:
> http://russellbryant.net/openstack-stats/tripleo-openreviews.html
>
>
> Stats since the last revision without -1 or -2 (ig
Hi everyone,
Two critical issues were discovered in Cinder RC2 testing, including one
that affected the ability to upgrade from a Grizzly setup. We fixed
those issues and published a new Havana release candidate for OpenStack
Block Storage ("Cinder").
You can find the RC3 tarball and the links to
Hi,
can you clarify your question? because without any l2-agent on your
compute host, your VM won't be able to communicate.
regards
On Tue, Oct 15, 2013 at 12:45 PM, B Veera-B37207 wrote:
> Hi,
>
>
>
> Vxlan endpoint ip is configured in
> ‘/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
Hi everyone,
One issue was discovered in Keystone RC2 testing, preventing Heat's
usage of trusts from being usable. We decided to fix this specific issue
pre-release and published a new Havana release candidate for OpenStack
Identity ("Keystone").
You can find the RC3 tarball and a link to the fi
On 16 October 2013 20:14, Alessandro Pilotti
wrote:>
>
> Drivers are IMO not part of the core of Nova, but completely separated and
> decoupled entities, which IMO should be treated that way. As a consequence,
> we frankly don't stricly feel as part of Nova, although some of us have a
> pretty
Hi all!
I already posted this message in the general mailing list, but I write it
here too.
I've made a simple network utility and I'd like to share it with the
community!
It's called "Show my network state" and it's a graphical network topology
visualizer for a single host.
I made it to simplify t
On Tue, Oct 15, 2013 at 09:21:12PM -0400, Mike Spreitzer wrote:
> Steve Baker wrote on 10/15/2013 06:48:53 PM:
>
> > From: Steve Baker
> > To: [email protected],
> > Date: 10/15/2013 06:51 PM
> > Subject: [openstack-dev] [Heat] HOT Software configuration proposal
> >
> > I've j
On Tue, Oct 15 2013, Sandy Walsh wrote:
> Hmm, I think I see your point. All the rabbit endpoints are determined
> by these switches:
> https://github.com/openstack/nova/blob/master/etc/nova/nova.conf.sample#L1532-L1592
>
> We will need a way in CM to pull from multiple rabbits.
This is a know li
On Tue, Oct 15, 2013 at 11:07:38PM -0500, Clark Laughlin wrote:
>
> I can see in config.py where VNC gets added (the element),
> but I can't find any place where a element gets added. In
> fact, I've grepped the entire nova tree for "cirrus" or "video" and
> can only find it here:
It is added
On Oct 16, 2013, at 11:19 , Robert Collins
mailto:[email protected]>>
wrote:
On 16 October 2013 20:14, Alessandro Pilotti
mailto:[email protected]>>
wrote:>
Drivers are IMO not part of the core of Nova, but completely separated and
decoupled entities, which IMO should
Sean Dague wrote:
> The Linux kernel process works for a couple of reasons...
>
> 1) the subsystem maintainers have known each other for a solid decade
> (i.e. 3x the lifespan of the OpenStack project), over a history of 10
> years, of people doing the right things, you build trust in their judgme
Dear all,
I've registered a new blueprint for nova-scheduler. The purpose of the
blueprint is to propose a new scheduler that is based on policy:
https://blueprints.launchpad.net/nova/+spec/policy-based-scheduler
With current Filter_Scheduler, admin cannot change his placement policy without
All,
There was a plan to use pypi's 'ordereddict' in Icehouse, to
replace how we're currently providing that functionality.
However, there are no ordereddict packages for Debian/Ubuntu
and there are no plans to provide them. (See Thomas Goirand's comment
here: https://review.openstack.org/#/c/48
On Oct 16, 2013, at 13:19 , Thierry Carrez
mailto:[email protected]>>
wrote:
Sean Dague wrote:
The Linux kernel process works for a couple of reasons...
1) the subsystem maintainers have known each other for a solid decade
(i.e. 3x the lifespan of the OpenStack project), over a history of
Alessandro, please fix your email program so that it does not send
HTML email to the list, and correctly quotes text you are replying
to with '> '. Your reply comes out looking like this which makes it
impossible to see who wrote what:
On Wed, Oct 16, 2013 at 10:42:45AM +, Alessandro Pilotti w
Alessandro Pilotti wrote:
> On Oct 16, 2013, at 13:19 , Thierry Carrez > The other two alternatives are to accept the delays and work within Nova
>> (slowly building the trust that will give you more autonomy), or ship it
>> as a separate add-on that does not come with nova-core's signature on it.
Daniel P. Berrange wrote:
> Alessandro, please fix your email program so that it does not send
> HTML email to the list, and correctly quotes text you are replying
> to with '> '.
+1 :)
Reference:
https://wiki.openstack.org/wiki/MailingListEtiquette
--
Thierry Carrez (ttx)
Sorry guys about this, my OS X Mail client had no issues
in doing the proper indentation, so I never noticed it. Darn.
I made a test with Daniel with a private email before spamming
here for nothing. Hope it worked out here as well.
Thanks for the heads up.
On Oct 16, 2013, at 13:47 , "Daniel
This sounds very similar to
https://blueprints.launchpad.net/nova/+spec/multiple-scheduler-drivers
We worked on it in Havana, learned a lot from feedbacks during the review
cycle, and hopefully will finalize the details at the summit and will be
able to continue & finish the implementation in
On Wed, Oct 16, 2013 at 6:49 PM, Robert Collins
wrote:
> On 16 October 2013 20:14, Alessandro Pilotti
> wrote:>
> >
>
> > Drivers are IMO not part of the core of Nova, but completely separated
> and decoupled entities, which IMO should be treated that way. As a
> consequence, we frankly don't str
Hi all,
We proposed a blueprint that supports API retry function with idenpotency for
Heat.
Prease review the blueprint.
https://blueprints.launchpad.net/heat/+spec/support-retry-with-idempotency
Any comments will be gratefully appreciated.
Regards.
Mitsuru Kanabuch
On Wed, Oct 16, 2013 at 8:49 PM, Thierry Carrez wrote:
> Sean Dague wrote:
> > The Linux kernel process works for a couple of reasons...
> >
> > 1) the subsystem maintainers have known each other for a solid decade
> > (i.e. 3x the lifespan of the OpenStack project), over a history of 10
> > years
On 10/16/2013 01:19 AM, Alessandro Pilotti wrote:
Sean, you got "called out" in the meeting not because you asked to put a
refernce link to the specs which was perfectly reasonable, but because
after we did what you asked for in a timely manner, you didn't bother to
review the patch again until
On 16/10/13 06:56, Mike Spreitzer wrote:
What is the difference between what today's heat engine does and a
workflow? I am interested to hear what you experts think, I hope it
will be clarifying. I presume the answers will touch on things like
error handling, state tracking, and updates.
(Dis
On 10/16/2013 07:40 AM, [email protected] wrote:
> All,
>
> There was a plan to use pypi's 'ordereddict' in Icehouse, to
> replace how we're currently providing that functionality.
>
> However, there are no ordereddict packages for Debian/Ubuntu
> and there are no plans to provide them. (Se
On 10/16/2013 01:45 AM, Vishvananda Ishaya wrote:
Hi Sean,
I'm going to top post because my response is general. I totally agree that we
need people that understand the code base and we should encourage new people to
be cross-functional. I guess my main issue is with how we get there. I believ
On Tue, Oct 15, 2013 at 5:44 PM, Kenichi Oomichi
wrote:
>
> Hi,
>
> # I resend this because gmail distinguished my previous mail as spam one..
>
> I'd like to know what validation feature is really needed for Nova v3 API,
> and I hope this mail will be a kick-off of brain-storming for it.
>
> << I
Has anyone looked into doing a effort in consolidating the different
implementations of these classes ?
Doing a short walk-through I see:
Manager
* Has a typical kind of API (server, lb, network, subnet) which it
interacts with and returns instances of a result as a Resource
Resource
* Repres
On Oct 16, 2013, at 15:16 , Sean Dague
wrote:
> On 10/16/2013 01:19 AM, Alessandro Pilotti wrote:
>
>>
>> Sean, you got "called out" in the meeting not because you asked to put a
>> refernce link to the specs which was perfectly reasonable, but because
>> after we did what you asked for in a
Hi there,
It appears that in Debian, python-coverage provides the wrapper in
/usr/bin/python-coverage. I tried to push the current maintainer to
provide /usr/bin/coverage, but he doesn't agree. He believes that
"coverage" is just too generic to be squatted by the python-coverage
package.
Robert C
It seems to me the much easier solution is to just always install
coverage.py into a virtualenv, then we don't have to worry at all about
operating-system politics.
Alex
On Wed, Oct 16, 2013 at 6:05 AM, Thomas Goirand wrote:
> Hi there,
>
> It appears that in Debian, python-coverage provides t
On 16/10/13 00:48, Steve Baker wrote:
I've just written some proposals to address Heat's HOT software
configuration needs, and I'd like to use this thread to get some feedback:
https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config
https://wiki.openstack.org/wiki/Heat/Blueprints/nati
On Wed, Oct 16, 2013 at 12:59:26PM +, Alessandro Pilotti wrote:
>
> When somebody (especially a core reviewer) puts a -1 and a new patch is
> committed to address it,
> I noticed that other reviewers wait for the guy that put the -1 to say
> something before +1/+2 it.
I think that depends
Folks:
A few of the key people cannot make today's ML2 meeting, so I'm going to cancel
it today. If you haven't filed your design summit sessions on ML2, please do so
by tomorrow! We have a list of them on the ML2 meeting page here [1] which we
collected over the past two weeks.
Also, Sukhdev
+1 to consolidate.
They are all doing the same thing, so why not put them into a common place?
>
*almost* the same thing, there's some small differences, one e.g is that
Ironic use PATH for the update instead of PUT.
Cheers,
Lucas
___
OpenStack-dev mai
Whoops, hit send too quickly. The Url for [2] is:
https://review.openstack.org/#/c/51992/
On Oct 16, 2013, at 8:19 AM, Kyle Mestery (kmestery) wrote:
> Folks:
>
> A few of the key people cannot make today's ML2 meeting, so I'm going to
> cancel it today. If you haven't filed your design summi
I can see though that there is a "apiclient" thing in oslo-incubator, would
it be an idea to name this oslo.client instead of having to copy this in
like other oslo stuff?
Endre
2013/10/16 Lucas Alvares Gomes
> +1 to consolidate.
>
> They are all doing the same thing, so why not put them into
Steven Hardy wrote on 10/16/2013 04:11:40 AM:
> ...
> IMO we should be abstracting the software configuration complexity
behind a
> Heat resource interface, not pushing it up to a pre-processor (which
> implies some horribly complex interfaces at the heat template level)
I am not sure I follow.
> +1 - I think we really want to have a strong preference for a stable
> api if we start separating parts out
So, as someone who is about to break the driver API all to hell over the
next six months (er, I mean, make some significant changes), I can tell
you that making it stable is the best way
Zane Bitter wrote on 10/16/2013 08:25:38 AM:
> To answer your question, the key thing that Heat does is take in two
> declarative models and generate a workflow to transform one into the
> other. (The general case of this is a stack update, where the two models
> are defined in the previous a
I also suggested using 'python -m coverage' which should work
everywhere without issue :)
-Rob
On 17 October 2013 02:05, Thomas Goirand wrote:
> Hi there,
>
> It appears that in Debian, python-coverage provides the wrapper in
> /usr/bin/python-coverage. I tried to push the current maintainer to
Tim,
Regarding this discussion, now there is at least a plan in Heat to allow
management of VMs not launched by that service:
https://blueprints.launchpad.net/heat/+spec/adopt-stack
So hopefully in future HARestarter will allow to support medium
availability for all types of instances.
--
Best r
Hi Steve,
thanks a lot taking the effort to write all this down. I had a look at both
wiki pages and have some comments below. This is really from the top of my
head, and I guess I have to spend some more time thinking about it, but I
wanted to provide some feedback anyway.
On "components vs. res
On Thu, Oct 17, 2013 at 12:21 AM, Dan Smith wrote:
> > +1 - I think we really want to have a strong preference for a stable
> > api if we start separating parts out
>
> So, as someone who is about to break the driver API all to hell over the
> next six months (er, I mean, make some significant ch
On Wed, Oct 16, 2013 at 06:51:50AM -0700, Dan Smith wrote:
> > +1 - I think we really want to have a strong preference for a stable
> > api if we start separating parts out
>
> So, as someone who is about to break the driver API all to hell over the
> next six months (er, I mean, make some signif
On 16/10/13 15:58, Mike Spreitzer wrote:
Zane Bitter wrote on 10/16/2013 08:25:38 AM:
> To answer your question, the key thing that Heat does is take in two
> declarative models and generate a workflow to transform one into the
> other. (The general case of this is a stack update, where the
Hi,
I am trying to install openstack on mutli node with help of devstack (
http://devstack.org/guides/multinode-lab.html).
I got some issues:
My setup details: One controller and One compute node (both VM).
OS - Ubuntu 13.04
Hello,
Just a quick update on the QoS API Extension - I plan on attending the
summit in Hong Kong and have registered a summit proposal to discuss the
current work that has been done.
Currently I have two reviews under way:
API Extension & Database models:
https://review.openstack.org/#/c/28313
Zane Bitter wrote on 10/16/2013 10:30:44 AM:
> On 16/10/13 15:58, Mike Spreitzer wrote:
> ...
> > Thanks for a great short sharp answer. In that light, I see a
concern.
> > Once a workflow has been generated, the system has lost the ability
to
> > adapt to changes in either model. In a high
On Wed, Oct 16, 2013 at 8:15 PM, Vikash Kumar <
[email protected]> wrote:
> Hi,
>
>I am trying to install openstack on mutli node with help of devstack (
> http://devstack.org/guides/multinode-lab.html).
>
>I got some issues:
>
> My setup details: One controller and One c
Ok - thank you, that helps.
- Clark
On Oct 16, 2013, at 3:21 AM, Daniel P. Berrange wrote:
> On Tue, Oct 15, 2013 at 11:07:38PM -0500, Clark Laughlin wrote:
>>
>> I can see in config.py where VNC gets added (the element),
>> but I can't find any place where a element gets added. In
>> fact,
Hi Sean
Just an FYI, we are also planning a QoS API Extension Blueprint for the
Icehouse Design Summit. Will hopefully submit that really soon. Perhaps we can
look at combining both of them and discuss this in Hong Kong as I have looked
over your BP and I can see some benefit in combining them
On Oct 16, 2013, at 9:54 AM, Sean M. Collins wrote:
> Hello,
>
> Just a quick update on the QoS API Extension - I plan on attending the
> summit in Hong Kong and have registered a summit proposal to discuss the
> current work that has been done.
>
> Currently I have two reviews under way:
>
> A
With regard to
https://blueprints.launchpad.net/oslo/+spec/i18n-messages
I think it would be helpful to define the high-level design
alternatives, before delving into technical details such as
"magic". To that end, here are the alternatives as I see them:
1. Attempt as much as possible to isolat
On 10/16/2013 08:59 AM, Alessandro Pilotti wrote:
When somebody (especially a core reviewer) puts a -1 and a new patch is
committed to address it,
I noticed that other reviewers wait for the guy that put the -1 to say
something before +1/+2 it.
My feeling on this is that if somebody reviews a
What fun would it be without late RCs...
We discovered that Keystone RC3 was still using lazy translations mode,
which could trigger errors in specific locales. Since all the other
projects in 2013.2 disabled this mode, we decided to fix this
pre-release and published a new Havana release candidat
On Wed, Oct 16, 2013 at 03:45:29PM +, Alan Kavanagh wrote:
> Will hopefully submit that really soon. Perhaps we can look at combining both
> of them and discuss this in Hong Kong as I have looked over your BP and I can
> see some benefit in combining them both.
Hi Alan,
That sounds great -
I'll be finalizing the design summit schedule [1] for keystone
following the weekly meeting [2] on Tuesday, October 22nd 18:00 UTC.
Please have your proposals submitted before then.
So far I think everyone has done a GREAT job self-organizing the
proposed sessions to avoid overlap, but we currentl
Hey folks,
I am sending an updated version of wireframes for Resource Class
Creation. Thanks everybody for your feedback, I tried to cover most of
your concerns and I am sending updated version for your reviews. If you
have any concerns, I am happy to discuss it with you.
http://people.redha
On 10/16/2013 12:31 PM, Jaromir Coufal wrote:
Hey folks,
I am sending an updated version of wireframes for Resource Class
Creation. Thanks everybody for your feedback, I tried to cover most of
your concerns and I am sending updated version for your reviews. If you
have any concerns, I am happy t
Hi Chris,
Thank you for your response.
2013/10/16 Christopher Yeoh
> On Tue, Oct 15, 2013 at 5:44 PM, Kenichi Oomichi <
> [email protected]> wrote:
>
>>
>> Hi,
>>
>> # I resend this because gmail distinguished my previous mail as spam one..
>>
>> I'd like to know what validation feature
Cheers Sean
I will take a look at the wiki and update accordingly. I took a look at your
BP, its right along the lines of what I feel is also needed and what we are
planning to submit (being finalised as I write this email) though we are also
adding some additional QoS attributes to be supporte
Just to clarify, the reason I believe it is important to lay out
high-level design alternatives and their implications is because it
will help in making decisions about how the Message class is to be
changed. In other words, the requirements for a class's behavior
might be drastically different, d
On Wed, Oct 16, 2013 at 11:23 AM, Dolph Mathews wrote:
> I'll be finalizing the design summit schedule [1] for keystone
> following the weekly meeting [2] on Tuesday, October 22nd 18:00 UTC.
> Please have your proposals submitted before then.
>
> So far I think everyone has done a GREAT job self-o
On 10/16/2013 12:23 PM, Dolph Mathews wrote:
I'll be finalizing the design summit schedule [1] for keystone
following the weekly meeting [2] on Tuesday, October 22nd 18:00 UTC.
Please have your proposals submitted before then.
So far I think everyone has done a GREAT job self-organizing the
prop
A partial slot to discuss how to achieve the vision in
https://wiki.openstack.org/wiki/DomainQuotaManagementAndEnforcement would be
useful.
The goal is to avoid duplicate effort which could be focused on a single theme.
With the various collaborations between HP, CERN and BARC along with Mira
Łukasz Jernaś wrote on 10/16/2013 02:26:28 AM:
> I'm still trying to wrap my head around the need for translating API
> messages and log messages as IMHO it adds a lot more problems for app
> developers and log analysis tools, eg. a log analysis tool would be
> usable only for the locale it was
On 2013-10-16 12:24, John S Warren wrote:
> Just to clarify, the reason I believe it is important to lay out
> high-level design alternatives and their implications is because it
> will help in making decisions about how the Message class is to be
> changed. In other words, the requirements
On Wed, Oct 16, 2013 at 1:19 PM, Ken'ichi Ohmichi wrote:
> Hi Chris,
>
> Thank you for your response.
>
> 2013/10/16 Christopher Yeoh
>
>> On Tue, Oct 15, 2013 at 5:44 PM, Kenichi Oomichi <
>> [email protected]> wrote:
>>
>>>
>>> Hi,
>>>
>>> # I resend this because gmail distinguished my
On Wed, Oct 16, 2013 at 2:04 PM, Mathew R Odden wrote:
> Łukasz Jernaś wrote on 10/16/2013 02:26:28 AM:
>
>
> > I'm still trying to wrap my head around the need for translating API
> > messages and log messages as IMHO it adds a lot more problems for app
> > developers and log analysis tools, e
On 10/16/2013 06:59 AM, Thierry Carrez wrote:
> Alessandro Pilotti wrote:
>> On Oct 16, 2013, at 13:19 , Thierry Carrez >> The other two alternatives are to accept the delays and work within Nova
>>> (slowly building the trust that will give you more autonomy), or ship it
>>> as a separate add-on t
Excerpts from Zane Bitter's message of 2013-10-16 06:16:33 -0700:
> On 16/10/13 00:48, Steve Baker wrote:
> > I've just written some proposals to address Heat's HOT software
> > configuration needs, and I'd like to use this thread to get some feedback:
> > https://wiki.openstack.org/wiki/Heat/Bluep
Hi Foks
I have setup baremetal nova and followed the instructions from the baremetal
wiki. Everything went fine till the last step ''nova boot ''. This
command ''nova boot'' is supposed to trigger the deployment process
as normal for nova. For the pxe baremetal driver that means extracti
Might be the last this time, if Horizon doesn't respin.
We discovered two issues in Neutron RC2, including one recent regression
with a security impact. We decided to fix these two pre-release and
published a new Havana release candidate for OpenStack Networking
("Neutron").
You can find the RC3
I guess the intention is to make VXLAN work with out quantum agent. It
means you are using an external openflow controller to manage OVS switches.
In such a case, there is a need to specifically get the compute node IP
from the VM data interface network( and not the management or openstack
network
On Wed, Oct 16, 2013 at 11:55 AM, John S Warren wrote:
> With regard to
> https://blueprints.launchpad.net/oslo/+spec/i18n-messages
>
> I think it would be helpful to define the high-level design
> alternatives, before delving into technical details such as
> "magic". To that end, here are the a
Ben Nemec wrote:
> Have you seen the discussion from the last Oslo meeting?
>
http://eavesdrop.openstack.org/meetings/oslo/2013/oslo.2013-10-11-14.00.log.txt
Unfortunately, I missed that meeting. I don't want to dwell on this
too much, but I would like add some thoughts that may not have
been c
Doug Hellmann wrote on 10/16/2013 03:11:12
PM:
>
> This doesn't quite match my understanding.
>
> IIUC, approach 1 was taken during havana and the resulting class did
> not behave enough like a string to work everywhere (specifically,
> with logging for locales that did not use UTF-8 or ASCI
Clint Byrum wrote on 10/16/2013 03:02:13 PM:
>
> Excerpts from Zane Bitter's message of 2013-10-16 06:16:33 -0700:
> >
> > For me the crucial question is, how do we define the interface for
> > synchronising and passing data from and to arbitrary applications
> > running under an arbitrary con
Hi All,
We had the FWaaS IRC meeting today, please check the logs if you could not
attend:
http://eavesdrop.openstack.org/meetings/networking_fwaas/2013/networking_fwaas.2013-10-16-18.01.log.html
We will have the next one same day/time (Wednesday 18:00 UTC/11 AM PDT)
next week, hope you can join
John S Warren/Raleigh/IBM@IBMUS wrote on 10/16/2013 03:38:05 PM:
> From: John S Warren/Raleigh/IBM@IBMUS
> To: OpenStack Development Mailing List
,
> Date: 10/16/2013 03:42 PM
> Subject: Re: [openstack-dev] [oslo] i18n Message improvements
>
> Doug Hellmann wrote on 10/16/2013 03:11:12
PM:
>
Hi,
As one of the next steps for PCI pass-through I would like to discuss is the
support for PCI pass-through vNIC.
While nova takes care of PCI pass-through device resources management and VIF
settings, neutron should manage their networking configuration.
I would like to register a summit prop
Thierry Carrez wrote:
> TC elections are underway and will remain open for you to cast your vote
> until at least 23:59 UTC on Thursday, October 17.
Reminder: voting closes in less than 27 hours.
--
Thierry Carrez (ttx)
___
OpenStack-dev mailing list
On 10/17/2013 02:16 AM, Zane Bitter wrote:
> On 16/10/13 00:48, Steve Baker wrote:
>> I've just written some proposals to address Heat's HOT software
>> configuration needs, and I'd like to use this thread to get some
>> feedback:
>> https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-conf
On 10/16/2013 02:05 PM, Thomas Goirand wrote:
> Hi there,
>
> It appears that in Debian, python-coverage provides the wrapper in
> /usr/bin/python-coverage. I tried to push the current maintainer to
> provide /usr/bin/coverage, but he doesn't agree. He believes that
> "coverage" is just too generi
Ad... last but not least, the Horizon respin!
We discovered a critical bug in Horizon RC2, preventing operation of
booted-from-volume instances. We decided to fix this issue pre-release
and published a new Havana release candidate for OpenStack Dashboard
("Horizon").
You can find the RC3 tarb
On 10/17/2013 03:11 AM, Thomas Spatzier wrote:
> Hi Steve,
>
> thanks a lot taking the effort to write all this down. I had a look at both
> wiki pages and have some comments below. This is really from the top of my
> head, and I guess I have to spend some more time thinking about it, but I
> wante
Hi Stackers,
We are thrilled to present to you Rally, the benchmarking system for
OpenStack.
It is not a secret that we have performance & scaling issues and that
OpenStack won’t scale out of box. It is also well known that if you get
your super big DC (5k-15k servers) you are able to find & fi
Hello Everyone,
I was wondering if there's a "standard" way within Neutron to retrieve tenants'
specific information (e.g. "name") from a plugin/service.
The call "context" already provides the tenant's UUID, but that may be useful
to have some extra info in certain cases.
Thanks,
Ivar.
___
I think this should be done in keystone. maybe you need a CLI command:
keystone tenant-get
On Thu, Oct 17, 2013 at 6:55 AM, Ivar Lazzaro wrote:
> Hello Everyone,
>
> ** **
>
> I was wondering if there’s a “standard” way within Neutron to retrieve
> tenants’ specific information (e.g. “name
I need to understand better what "holistic scheduling" means, but I agree
with you that this is not exactly what Boris has raised as an issue. I
don't have a rock solid design for what I want to do, but at least the
objectives I want to achieve are that spinning up more schedulers increases
your re
As Yongsheng said, use keystone tenant-list. We overload keystone tenant
with lot more tenant specific information as metadata and use it in other
openstack services.
On Wed, Oct 16, 2013 at 4:11 PM, Yongsheng Gong wrote:
> I think this should be done in keystone. maybe you need a CLI command:
>
Hi all,
The [state-management] project team holds a weekly meeting in
#openstack-meeting on thursdays, 2000 UTC. The next meeting is tomorrow,
2013-10-17!!!
As usual, everyone is welcome :-)
Link: https://wiki.openstack.org/wiki/Meetings/StateManagement
Taskflow: https://wiki.openstack.org/Tas
Hi,
I'd like to support linuxbridge QoS.
I submmited the following BP:
https://blueprints.launchpad.net/neutron/+spec/ml2-qos-linuxbridge
I won't attend the summit but Toshihiro, my co-worker will attend
the summit and attend the QoS session.
Thanks.
Itsuro Oda
On Wed, 16 Oct 2013 17:21:36 +0
Mike Wilson wrote on 10/16/2013 07:13:17 PM:
> I need to understand better what "holistic scheduling" means, ...
By "holistic" I simply mean making a joint decision all at once about a
bunch of related resources of a variety of types. For example, making a
joint decision about where to place
I agree that likely extensions and internal API discussions can become one
session. I think the API side of that won't need to fill a whole session.
On Wednesday, October 16, 2013, Adam Young wrote:
> On 10/16/2013 12:23 PM, Dolph Mathews wrote:
>
>> I'll be finalizing the design summit schedule
Excerpts from Mitsuru Kanabuchi's message of 2013-10-16 04:47:08 -0700:
>
> Hi all,
>
> We proposed a blueprint that supports API retry function with idenpotency for
> Heat.
> Prease review the blueprint.
>
> https://blueprints.launchpad.net/heat/+spec/support-retry-with-idempotency
>
This
99 matches
Mail list logo
