On 09/01/15 12:11 -0800, Joshua Harlow wrote:
So the only comment I'll put in is one that I know not everyone agrees
with but might as well throw it out there.
http://freenode.net/channel_guidelines.shtml (this page has a bunch of
useful advice IMHO).
From that; something useful to
There was a discussion on whether to put all the fuel plugins into the
single repository or have them separate. The problems with all the fuel
plugins in single repository are following:
- it is impossible to make a branch on a single plugin, branch is applied
to the whole repository and all the
Hi Alan,
We are now in the process of doing It :)
Thanks
Vikram
From: lv.erc...@zte.com.cn [mailto:lv.erc...@zte.com.cn]
Sent: 12 January 2015 12:57
To: Vikram Choudhary
Cc: Dongfeng (C); Dhruv Dhody; Kalyankumar Asangi; OpenStack Development
Mailing List (not for usage questions);
On 01/09/2015 08:12 PM, Stefano Maffulli wrote:
Dear all,
if you've tried the topics on this mailing list and haven't received
emails, well... we had a problem on our side: the topics were not setup
correctly.
Luigi Toscano helped isolate the problem and point at the solution[1].
He noticed
Hi Ian,
Spec for “Support vhost-user in libvirt vif driver” [1] has been approved for
Kilo. We should have code available by EOW.
We are also working on a mechanism driver for Neutron as well [2]. We started
working on a 3rd party CI.
Regards
Przemek
[1]
On 01/08/2015 10:22 AM, Derek Higgins wrote:
On 07/01/15 23:41, Ben Nemec wrote:
I don't feel like we've been all that capacity constrained lately
anyway, so as I said in my other (largely unnecessary, as it turns out)
email, I'm +1 on doing this.
Correct we're not currently constrained on
On 09/01/15 15:50 +0100, Thierry Carrez wrote:
[huge snip]
What do you think ? Could that work ? If not, do you have alternate
suggestions ?
Love it! Thanks for the thoughtful and detailed email.
Flavio
--
@flaper87
Flavio Percoco
pgp2LB9GMnSpn.pgp
Description: PGP signature
Hi all,
I am still getting the same error while installing the Openstack through
devstack, If someone know the solution please reply.
On Fri, Jan 9, 2015 at 1:53 PM, Abhishek Shrivastava abhis...@cloudbyte.com
wrote:
Hi Liuxinguo,
Thanks for the suggestion, I'll try and make it work.
On
On Fri, Jan 09, 2015 at 09:15:39AM +0800, Lingxian Kong wrote:
There is an excellent post describing this, for your information:
http://blog.oddbit.com/2014/12/22/accessing-the-serial-console-of-your-nova-servers/
In the last section of that article he describes my issue as well:
It would
Tim Bell wrote:
Let's ask the operators opinions too on openstack-operators mailing list.
Sure, that's my next step. I first wanted to check that this change was
fine for historic Design Summit participants. I'll follow up with
operators and also discuss it at the Ops meetup.
FWIW, the
Hi,
We decided to cancel today’s team meeting because some key members of the team
won’t be present.
The next on will be held on Jan 19.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for
Hello.
We are working on the modularization of Openstack deployment by puppet
manifests in Fuel library [0].
Each deploy step should be post-verified with some testing framework as
well.
I believe the framework should:
* be shipped as a part of Fuel library for puppet manifests instead of
On Fri, Jan 9, 2015 at 8:50 AM, Thierry Carrez thie...@openstack.org
wrote:
Hi everyone,
The OpenStack Foundation staff is considering a number of changes to the
Design Summit format for Vancouver, changes on which we'd very much like
to hear your feedback.
The problems we are trying to
On Mon, Jan 12, 2015 at 3:33 PM, Angus Salkeld asalk...@mirantis.com
wrote:
On Mon, Jan 12, 2015 at 10:17 PM, Konstantin Danilov
kdani...@mirantis.com wrote:
Boris,
Move from sync http to something like websocket requires a lot of work
and not directly connected
with API issue. When
Folks:
During tomorrow's Neutron meeting, I'd like to spend a little time going
over the approved specs marked as Critical and High priority [1]. We're
about 3 weeks out from Kilo-2, so I'd like to get a feel for how these are
coming along. If you are assigned one of these specs and can't make
Hello all,
in Paris (and later on, on IRC and the mailing list) I began to ask around
about providing a DRBD storage driver for Nova.
This is an alternative to using iSCSI for block storage access, and would
be especially helpful for backends already using DRBD for replicated
storage.
The
Hi,
Puppet OpenStack community uses Beaker for acceptance testing. I would
consider it as option [2]
[2] https://github.com/puppetlabs/beaker
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Mon, Jan 12, 2015 at 2:53 PM, Bogdan Dobrelya bdobre...@mirantis.com
wrote:
Hello.
--
Message: 16
Date: Wed, 31 Dec 2014 17:41:10 -0800
From: Andrew Woodward xar...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Fuel][plugins] Fuel 6.0 plugin
Folks,
as it was planned and then announced at the OpenStack summit OpenStack services
deprecated Python-2.6 support. At the moment several services and libraries are
already only compatible with Python=2.7. And there is no common sense in
trying to get back compatibility with Py2.6 because
Hello,
Andrew, thank you for pointing out all the issues. I left more
detailed comments inlined
On Tue, Jan 6, 2015 at 3:51 AM, Andrew Woodward xar...@gmail.com wrote:
Here is a list of the issues I ran into using IBP before the 23rd. 5
appears to not be merged yet and must be resolved prior
On Mon, Jan 12, 2015 at 10:17 PM, Konstantin Danilov kdani...@mirantis.com
wrote:
Boris,
Move from sync http to something like websocket requires a lot of work and
not directly connected
with API issue. When openstack api servers begin to support
websockets - it would be easy to change
Hi,
Regarding the last issue, i fixed it by logging in and manually pip
install docutils. Image was created successfully.
Now the problem is that nodepool is not able to login into instances
created from that image.
I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running,
and
Hi Vladik,
I added the [Telco] tag.
see below..
Am 12.01.2015 um 03:02 schrieb Vladik Romanovsky
vladik.romanov...@enovance.com:
Hi everyone,
Following Steve Gordon's email [1], regarding CI for NUMA, SR-IOV, and other
features, I'd like to start a discussion about the NUMA testing in
https://review.openstack.org/#/c/127609/
This is a fundamental building block for the #3 priority (Scheduler)
work in Kilo. It's been through 11 revisions so far and has support from
at least one nova-driver and 4 non-drivers.
This work is a building block for the scheduler because it
On Mon, Jan 12, 2015 at 02:47:19PM +0100, Marc Koderer wrote:
Hi Vladik,
I added the [Telco] tag.
see below..
Am 12.01.2015 um 03:02 schrieb Vladik Romanovsky
vladik.romanov...@enovance.com:
Hi everyone,
Following Steve Gordon's email [1], regarding CI for NUMA, SR-IOV, and
Hi Yuriy,
FYI there is a project proposal on opnfv wiki on this issue:
https://wiki.opnfv.org/requirements_projects/openstack_based_vnf_forwarding_graph
On Wed, Jan 7, 2015 at 12:22 AM, yuriy.babe...@telekom.de wrote:
Hi all,
as discussed per last IRC meeting we prepared first thoughts on
Since it seems a permission error, this may help:
http://docs.openstack.org/developer/devstack/guides/single-machine.html#installation-shake-and-bake
NB: in my environment I had to edit the file sudoers with a text editor
(echoing the string didn't work).
On 01/12/15 09:33, Abhishek Shrivastava
Whats the log now?
On Mon, Jan 12, 2015 at 4:53 PM, Abhishek Shrivastava
abhis...@cloudbyte.com wrote:
Hi Samta,
Thanks for the suggestion but still problem remains the same.
On Mon, Jan 12, 2015 at 4:29 PM, Samta Rangare samtarang...@gmail.com
wrote:
Hey abhishek,
As a quick fix to
Hi,
Back with another error during image creation with nodepool:
2015-01-12 13:05:17,775 INFO nodepool.image.build.local_01.d-p-c:
Downloading python-daemon-2.0.1.tar.gz (62kB)
2015-01-12 13:05:18,022 INFO nodepool.image.build.local_01.d-p-c:
Traceback (most recent call last):
2015-01-12
I tried that also but still the error is same.
On Mon, Jan 12, 2015 at 3:32 PM, Pasquale Porreca
pasquale.porr...@dektech.com.au wrote:
Since it seems a permission error, this may help:
http://docs.openstack.org/developer/devstack/guides/single-machine.html#installation-shake-and-bake
NB:
Hi,
Can anyone explain the difference between gbp group-create and gbp
policy-target-group-create??
I think both these are working same.
Thanks Regards
Sachi Gupta
From: Sumit Naiksatam sumitnaiksa...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
Its showing the same error on Ubuntu 13.10, so I think its not a Ubuntu
Version issue.
On Mon, Jan 12, 2015 at 4:02 PM, Amit Das amit@cloudbyte.com wrote:
Is this related to the version of Ubuntu being used ?
Its 12.04 as per the email.
Regards,
Amit
*CloudByte Inc.*
Konstantin,
I believe it's better to work on server side, and use some modern approach
like web sockets for async operations. So we won't need to retrieve 100500
times information about object. And then use this feature in clients.
create_future = novaclient.servers.create_async()
Is this related to the version of Ubuntu being used ?
Its 12.04 as per the email.
Regards,
Amit
*CloudByte Inc.* http://www.cloudbyte.com/
On Mon, Jan 12, 2015 at 3:55 PM, Abhishek Shrivastava
abhis...@cloudbyte.com wrote:
I tried that also but still the error is same.
On Mon, Jan 12, 2015
Hi guys,
Thanks for answering my questions. I have 2 points:
1 - This (remove drivers without CI) is a way impacting change to be
implemented without exhausting notification and discussion on the mailing
list. I myself was in the meeting but this decision wasn't crystal clear.
There must be
Hi all.
There a set of openstack api functions which starts background actions
and return preliminary results - like 'novaclient.create'. Those functions
requires periodically check results and handle timeouts/errors
(and often cleanup + restart help to fix an error).
Check/retry/cleanup code
Hi Samta,
Thanks for the suggestion but still problem remains the same.
On Mon, Jan 12, 2015 at 4:29 PM, Samta Rangare samtarang...@gmail.com
wrote:
Hey abhishek,
As a quick fix to this problem, edit this file devstack/lib/keystone +170
in this function
function configure_keystone {
edit
Same as before.
On Mon, Jan 12, 2015 at 5:04 PM, Samta Rangare samtarang...@gmail.com
wrote:
Whats the log now?
On Mon, Jan 12, 2015 at 4:53 PM, Abhishek Shrivastava
abhis...@cloudbyte.com wrote:
Hi Samta,
Thanks for the suggestion but still problem remains the same.
On Mon, Jan 12,
Boris,
Move from sync http to something like websocket requires a lot of work and
not directly connected
with API issue. When openstack api servers begin to support
websockets - it would be easy to change implementation of monitoring thread
without breaking compatibility.
At the moment periodical
You rock, man. Thanks, I'll steal those. :)
/Ihar
On 01/11/2015 09:39 PM, Davanum Srinivas wrote:
Jay,
I have a hacking rule in nova already [1] and am updating the rule in
the 3 reviews i have for oslo_utils, oslo_middleware and oslo_config
[2] in Nova
thanks,
dims
[1]
Is your root filesystem full? The log clearly shows the chown stack
/etc/keystone passing right before the copy is attempted.
-Sean
On 01/12/2015 06:59 AM, Abhishek Shrivastava wrote:
Same as before.
On Mon, Jan 12, 2015 at 5:04 PM, Samta Rangare samtarang...@gmail.com
Hey abhishek,
As a quick fix to this problem, edit this file devstack/lib/keystone +170
in this function
function configure_keystone {
edit this line with adding sudo
sudo cp -p $KEYSTONE_DIR/etc/keystone.conf.sample $KEYSTONE_CONF
Regards
Samta
On Mon, Jan 12, 2015 at 4:01 PM, Abhishek
Hi folks!
This is a status update.
Right now the patch for creating a new project on Stackforge is blocked by a
bug in Zuul [1] which is actually a bug in python-daemon, the patch for this is
already published [2] and waiting for being approved.
After the patch is merged and all projects and
On Mon, Jan 12, 2015 at 06:28:53PM +0300, Dmitry Guryanov wrote:
On 01/05/2015 02:30 PM, Daniel P. Berrange wrote:
On Tue, Dec 30, 2014 at 05:18:19PM +0300, Dmitry Guryanov wrote:
Hello,
Libvirt can create loop or nbd device for LXC container and mount it by
itself, for instance, you can
On 01/12/2015 10:29 AM, Tomas Sedovic wrote:
Hey folks,
I did a quick proof of concept for a part of the Stack Breakpoint
spec[1] and I put the does this resource have a breakpoint flag into
the metadata of the resource:
https://review.openstack.org/#/c/146123/
I'm not sure where this
+1 to Flavio's proposal.
Thanks,
-Nikhil
From: Flavio Percoco [fla...@redhat.com]
Sent: Monday, January 12, 2015 3:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Glance] IRC logging
On 09/01/15 12:11
On 01/05/2015 02:30 PM, Daniel P. Berrange wrote:
On Tue, Dec 30, 2014 at 05:18:19PM +0300, Dmitry Guryanov wrote:
Hello,
Libvirt can create loop or nbd device for LXC container and mount it by
itself, for instance, you can add something like this to xml config:
filesystem type='file'
There's really no way to _force_ official logging on all
project-related channels. People who are opposed to the idea simply
move their conversations to new channels. They'll straddle the line
between somewhat official looking and official enough to require
logging.
--
Jeremy Stanley
Hi, Roman,
Indeed, we have to go forward and drop python 2.6 support. That's how
it supposed to be, but, unfortunately, it may not be as easy as it
seems at first glance.
Fuel Master is flying on top of Cent OS 6.5 which doesn't have python
2.7 at all. So we must either run master node on Cent
The public link for your test logs should really be a host name instead of
an IP address. That way if you have to change it again in the future, you
won't have dead links in old comments. You may already know, but all of the
requirements and recommendations are here:
On Mon, Jan 12, 2015 at 10:03 AM, Nikesh Kumar Mahalka
nikeshmaha...@vedams.com wrote:
Hi,
We deployed a kilo devstack on ubuntu 14.04 server.
We successfully launched a instance from dashboard, but we are unable to
open console from dashboard for instance.Also instacne is unable to get ip
After some discussion with Sean Dague and a few others it became
clear that it would be a good idea to introduce a new tool I've been
working on to the list to get a sense of its usefulness generally,
work towards getting it into global requirements, and get the
documentation fleshed out so that
This is a reminder that the Keystone spec proposal deadline is Feb 5. Please
work to have your specs submitted and approved by that date.
The keystone team will be spending time at the midcycle next week (Jan 19, 20,
21) to discuss specs; specs proposed before the midcycle will get priority
On 09/01/15 07:06, Gregory Haynes wrote:
Excerpts from Steven Hardy's message of 2015-01-08 17:37:55 +:
Hi all,
I'm trying to test a fedora-software-config image with some updated
components. I need:
- Install latest master os-apply-config (the commit I want isn't released)
- Install
After some discussion with Sean Dague and a few others it became
clear that it would be a good idea to introduce a new tool I've been
working on to the list to get a sense of its usefulness generally,
work towards getting it into global requirements, and get the
documentation fleshed out so
On Jan 12, 2015, at 9:55 AM, Roman Prykhodchenko m...@romcheg.me wrote:
Folks,
as it was planned and then announced at the OpenStack summit OpenStack
services deprecated Python-2.6 support. At the moment several services and
libraries are already only compatible with Python=2.7. And
Hello,
I'd like to request an exception for virtio-net multiqueue feature. [1]
This is an important feature that aims to increase the total network throughput
in guests and not too hard to implement.
Thanks,
Vladik
[1] https://review.openstack.org/#/c/128825
Thanks for this Chris, I'm hoping to get my fingers dirty with it Real Soon
Now.
On Mon, Jan 12, 2015 at 1:54 PM, Eoghan Glynn egl...@redhat.com wrote:
I'd be interested in hearing the api-wg viewpoint, specifically whether
that working group intends to recommend any best practices around the
On 01/12/2015 03:11 PM, Dean Troyer wrote:
Thanks for this Chris, I'm hoping to get my fingers dirty with it Real
Soon Now.
On Mon, Jan 12, 2015 at 1:54 PM, Eoghan Glynn egl...@redhat.com
mailto:egl...@redhat.com wrote:
I'd be interested in hearing the api-wg viewpoint, specifically
On 01/12/2015 03:18 PM, Boris Pavlovic wrote:
Chris,
The Idea is brilliant. I may steal it! =)
But there are some issues that will be faced:
1) Using as a base unittest:
python -m subunit.run discover -f gabbi | subunit2pyunit
So rally team won't be able to reuse it for
Sean,
I definitely like the direction that gabbi seems to be headed. It feels
like a much cleaner version of what nova tried to do with API samples.
As long as multiple projects think this is an interesting direction, I
think it's probably fine to add it to global-requirements and let them
Excerpts from Chris Dent's message of 2015-01-12 19:20:18 +:
After some discussion with Sean Dague and a few others it became
clear that it would be a good idea to introduce a new tool I've been
working on to the list to get a sense of its usefulness generally,
work towards getting it
On 12/18/14 6:58 AM, Radomir Dopieralski wrote:
Hello,
revisiting the package management for the Horizon's static files again,
I would like to propose a particular solution. Hopefully it will allow
us to both simplify the whole setup, and use the popular tools for the
job, without losing
On Mon, 12 Jan 2015, Gregory Haynes wrote:
Awesome! I was discussing trying to add extensions to RAML[1] so we
could do something like this the other day. Is there any reason you
didnt use an existing modeling language like this?
Glad you like it.
I chose to go with my own model in the YAML
Hello TC,
I would like to propose to allow adding all python-clients from stackforge
(that are regarding global-requirements) to global requirements.
It doesn't cost anything and simplifies life for everybody on stackforge.
P.S. We already have billions libs in global requirements that aren't
The Keystone development team is looking for deployment feedback regarding the
use of the LDAP Identity backend. The Identity backend only covers Users and
Groups.
We are looking to get an idea of types (read-only, read-write, etc) and reasons
for use of the LDAP backend. The answers to this
Just a heads up for anyone else making these changes: Even though the
g-r entry is =0.10, you need to do =0.10.0 in the project for it to
pass the requirements check.
On 01/10/2015 07:15 PM, Joe Gordon wrote:
Hi all,
I am happy to announce the release of hacking 0.10. Below is a list of
Chris,
The Idea is brilliant. I may steal it! =)
But there are some issues that will be faced:
1) Using as a base unittest:
python -m subunit.run discover -f gabbi | subunit2pyunit
So rally team won't be able to reuse it for load testing (if we directly
integrate it) because we will have
Hi.
I'm testing OpenStack setup set on our hardware with Fuel 6.0 and I found the
problem with 10Gbit network interfaces configuration.
Our setup uses Centos on deployed nodes - I didn't look how this situation
looks from Ubuntu perspective, but looking on the fuel-library - there is
probably
On 12/01/15 10:49, Ryan Brown wrote:
On 01/12/2015 10:29 AM, Tomas Sedovic wrote:
Hey folks,
I did a quick proof of concept for a part of the Stack Breakpoint
spec[1] and I put the does this resource have a breakpoint flag into
the metadata of the resource:
On Tue, 13 Jan 2015, Boris Pavlovic wrote:
The Idea is brilliant. I may steal it! =)
Feel free.
But there are some issues that will be faced:
1) Using as a base unittest:
python -m subunit.run discover -f gabbi | subunit2pyunit
So rally team won't be able to reuse it for load testing
Hi Chris,
If there's sufficient motivation and time it might make sense to
separate the part of gabbi that builds TestCases from the part that
runs (and evaluates) HTTP requests and responses. If that happens then
integration with tools like Rally and runners is probably possible.
Having
On 12/01/15 13:05, Steven Hardy wrote:
I also had a chat with Steve Hardy and he suggested adding a STOPPED state
to the stack (this isn't in the spec). While not strictly necessary to
implement the spec, this would help people figure out that the stack has
reached a breakpoint instead of just
On 01/12/2015 05:00 PM, Boris Pavlovic wrote:
Hi Chris,
If there's sufficient motivation and time it might make sense to
separate the part of gabbi that builds TestCases from the part that
runs (and evaluates) HTTP requests and responses. If that happens then
integration
On 09:03 Mon 12 Jan , Erlon Cruz wrote:
Hi guys,
Thanks for answering my questions. I have 2 points:
1 - This (remove drivers without CI) is a way impacting change to be
implemented without exhausting notification and discussion on the mailing
list. I myself was in the meeting but
On 1/9/15, 15:17, Everett Toews everett.to...@rackspace.com wrote:
One thing that has come up in the past couple of API WG meetings [1] is
just how useful a proper API definition would be for the OpenStack
projects.
By API definition I mean a format like Swagger, RAML, API Blueprint, etc.
These
On Mon, Jan 12, 2015 at 1:20 PM, Chris Dent chd...@redhat.com wrote:
After some discussion with Sean Dague and a few others it became
clear that it would be a good idea to introduce a new tool I've been
working on to the list to get a sense of its usefulness generally,
work towards getting
On Mon, Jan 12, 2015 at 05:10:47PM -0500, Zane Bitter wrote:
On 12/01/15 13:05, Steven Hardy wrote:
I also had a chat with Steve Hardy and he suggested adding a STOPPED state
to the stack (this isn't in the spec). While not strictly necessary to
implement the spec, this would help people
On Mon, 12 Jan 2015, Anne Gentle wrote:
I'm interested, sure. What did you use to write the HTTP tests, as in, what
was the source of truth for what the requests and responses should be?
That is an _extremely_ good question and one I really struggled with
as I started integrating gabbi with
Sean,
So I'd say let's focus on that problem right now, and get some traction
on this as part of functional test suites in OpenStack. Genericizing it
too much just turns this back into a version of every other full stack
testing tool, which we know isn't sufficient for having quality
Hi,
I’m canceling the meeting since I’m traveling this week.
Regards,
Robert
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
On Mon, 12 Jan 2015, Ian Cordasco wrote:
This worked extremely well in my experience and helped improve development
time for new endpoints and new endpoint versions. The documentation was
also heavily used for the multiple internal clients for that API.
This idea of definition formats seems
I was also thinking of using the environment to hold the breakpoint,
similarly to parameters. The CLI and API would process it just like
parameters.
As for the state of a stack hitting the breakpoint, leveraging the
FAILED state seems to be sufficient, we just need to add enough
Hi,
With [1] merged, we now have people working on creating external
plugins for devstack.
I worry about use of arbitrary external locations as plugins for gate
jobs. If a plugin is hosted externally (github, bitbucket, etc) we
are introducing a whole host of problems when it is used as a gate
On Tue, 13 Jan 2015, Boris Pavlovic wrote:
Having separated engine seems like a good idea. It will really simplify
stuff
I'm not certain that's the case, but it may be worth exploration.
This seems like a huge duplication of efforts. I mean operators will write
own
tools developers own...
On 1/12/15, 17:21, Chris Dent chd...@redhat.com wrote:
On Mon, 12 Jan 2015, Ian Cordasco wrote:
This worked extremely well in my experience and helped improve
development
time for new endpoints and new endpoint versions. The documentation was
also heavily used for the multiple internal
0.9.2 was blocked because of a change that broke unit tests in some
projects, that is fixed in 0.9.4.
What happened to 0.9.3? Problems, don't ask - fixed in 0.9.4 (thanks
mordred).
Changes:
mriedem@ubuntu:~/git/sqlalchemy-migrate$ git log --no-merges --oneline
0.9.2..0.9.4
b011e6c Remove
Hi,
This spec[1] is for adding JSON-Home feature to Nova v2.1 API.
This feature will provide API resource information with a
standard way which has been already implemented in Keystone.
I hope this feature will promote that people use v2.1 API in production
environments.
I created a prototype[2]
2015-01-13 13:57 GMT+08:00 少合冯 lvmxhs...@gmail.com:
Hello,
I'd like to request an exception for Attach/Detach SR-IOV interface
feature. [1]
This is an important feature that aims to improve better performance than
normal
network interface in guests and not too hard to implement.
Thanks,
On 12/01/15 21:53, Drew Fisher wrote:
I know I'm very very late to this thread but can I ask why Bower? Bower
has a hard requirement on Node.js which was removed as a dependency in
Havana. Why are we reintroducing this requirement?
For Solaris, a requirement on Node.js is especially
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Remove direct nova DB/API access by Scheduler Filters -
https://review.opernstack.org/138444/
2) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo
3) Topics for mid-cycle meetup
--
Don Dugger
Censeo
Hello,
I'd like to request an exception for Attach/Detach SR-IOV interface
feature. [1]
This is an important feature that aims to improve better performance than
normal
network interface in guests and not too hard to implement.
Thanks,
Shao He, Feng
[1] https://review.openstack.org/#/c/139910/
Hi,
The ironic needs this feature from nova to implement Firmware settings.
The code also has been proposed for the same.
Spec link: https://review.openstack.org/133534
Code link: https://review.openstack.org/141010
Regards
Nisha
--
The Secret Of Success is learning how to use pain and
Hello,
I'd like to request an exception for Attach/Detach SR-IOV interface
feature. [1]
This is an important feature that aims to improve better performance than
normal
network interface in guests and not too hard to implement.
Thanks,
Shao He, Feng
[1] https://review.openstack.org/#/c/139910/
On 01/12/2015 03:55 PM, Roman Prykhodchenko wrote:
Folks,
as it was planned and then announced at the OpenStack summit OpenStack services
deprecated Python-2.6 support. At the moment several services and libraries are
already only compatible with Python=2.7. And there is no common sense in
2015-01-13 13:57 GMT+08:00 少合冯 lvmxhs...@gmail.com:
Hello,
I'd like to request an exception for Attach/Detach SR-IOV interface
feature. [1]
This is an important feature that aims to improve better performance than
normal
network interface in guests and not too hard to implement.
Thanks,
https://review.openstack.org/#/c/127863/
This spec is part of Nova REST API policy improvement. And those
improvement already got generic agreement as in this full view devref
https://review.openstack.org/#/c/138270/
This spec is just for Nova REST API v2.1. So really hope it can be done
before
Hello, Sachi,
They both works. End point group has been renamed to policy target group.
It is recommended to use gbp policy-target-group-create.
Yapeng
From: Sachi Gupta [mailto:sachi.gu...@tcs.com]
Sent: Monday, January 12, 2015 7:03 AM
To: OpenStack Development Mailing List (not for usage
You are correct to run nodepoold as nodepool user.
I didn’t see any issues…
Could you double check the public keys listed in .ssh/authorized_keys in the
template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
Ramy
From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Monday,
On Mon, Jan 12, 2015 at 04:29:15PM +0100, Tomas Sedovic wrote:
Hey folks,
I did a quick proof of concept for a part of the Stack Breakpoint spec[1]
and I put the does this resource have a breakpoint flag into the metadata
of the resource:
https://review.openstack.org/#/c/146123/
I'm
1 - 100 of 114 matches
Mail list logo
