, if in localrc if you've already overridden it there), or just call
`enable_service n-novnc` in localrc.
Best Regards,
Solly Ross
- Original Message -
From: Chen Li chen...@intel.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Hi!
I just wanted to note that noVNC 0.5.1 is slated to be in Fedora 22 and
is currently in EPEL testing for EPEL 6 and EPEL 7
(https://apps.fedoraproject.org/packages/novnc).
Best Regards,
Solly Ross
- Original Message -
From: Nathan Kinder nkin...@redhat.com
To: OpenStack
Double-check no make sure that it's enabled. A couple months ago, noVNC got
removed from the standard install because devstack was installing it from
GitHub.
- Original Message -
From: Chen Li chen...@intel.com
To: OpenStack Development Mailing List (not for usage questions)
not use any modules from oslo-incubator, and it is unclear
what
constitutes an appropriate script.
Best Regards,
Solly Ross
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
Those scripts have mostly moved into oslotest, so they don't need to be
synced any more to be used. If you have all of your code, and it follows
the cookiecutter template, we can look at it and propose post-import
tweaks. What's the URL for the repository?
Heh, whoops. I should probably
.
Best Regards,
Solly Ross
[1]
http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/use-libvirt-storage-pools.html
[2] https://review.openstack.org/#/c/152348/ and onward
P.S. I would really like to get this in, since this would be the second time
that
this has been deferred
using the VeNCrypt RFB auth method.
The two patches [2] have sat in place with one +2 (Dan Berrange) and multiple
+1s
for a while now (the first does not currently show any votes because of a merge
conflict that I had to deal with recently).
Best Regards,
Solly Ross
[1]
http
If you rewrite the noNVC installation in devstack to work from a release
URL that includes the released version on it, I think that would be
sufficient to turn it back on. Again, ideally this should be in distros,
but I think we could work on doing release installs until then,
especially if
?
Best Regards,
Solly Ross
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
be accidental (either through habit or through accidentally
pressing the key).
Best Regards,
Solly Ross
- Original Message -
From: Aaron Sahlin asah...@linux.vnet.ibm.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, December
time in reading this e-mail, in strong terms
if necessary :)
I dislike using strong terms ;-), but I do think you may have misread the
spec.
If you are unclear, you can catch me next week on freenode as directxman12 and
we can discuss further (I'm out on PTO this week).
Best Regards,
Solly Ross
just say use the
XYZ image and you're all set (although this could be an argument for using
Heat templates as well).
Best Regards,
Solly Ross
- Original Message -
From: Blair Bethwaite blair.bethwa...@gmail.com
To: openstack-dev@lists.openstack.org
Sent: Tuesday, November 25, 2014 5:15
Whoops, that should say assertions not exceptions.
- Original Message -
From: Solly Ross sr...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, November 24, 2014 12:00:44 AM
Subject: Re: [openstack-dev] [nova
Well, at least the message for exceptions in Nova says expected and
observed.
I suspect that it's part of our custom test case classes.
Best Regards,
Solly Ross
- Original Message -
From: Matthew Treinish mtrein...@kortar.org
To: OpenStack Development Mailing List (not for usage
I've been working on
the related code recently.
Best Regards,
Solly Ross
- Original Message -
From: Vishvananda Ishaya vishvana...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, November 18, 2014 4:07:31 PM
Hello Doug et all,
I would like to get the ball rolling on graduating oslo-incubator/reports into
oslo.reports. What do I have to do on my end to move forward with the
graduation
process?
Best Regards,
Solly Ross
___
OpenStack-dev mailing list
The serial proxy will not automatically start. It's intended to be started as
a service, just the like API, VNC proxy, or SPICE proxy.
Best Regards,
Solly Ross
- Original Message -
From: Markus Zoeller mzoel...@de.ibm.com
To: OpenStack Development Mailing List (not for usage
You should be able to connect like a normal WebSocket, assuming you're running
the serial console websocketproxy (it's a different command from the VNC web
socket proxy). If you want, you can ping
on IRC and I can help you debug your JS code.
Best Regards,
Solly Ross
(directxman12 on freenode
backends,
while critical-data might be on a large general-purpose backend.
Best Regards,
Solly Ross
- Original Message -
From: Alexander Tivelkov ativel...@mirantis.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday
For future reference, it looks like you had an old version of websockify
installed that wasn't getting updated, for some reason. Nova recently accepted
a patch that removed the support for the old version of websockify
Best Regards,
Solly Ross
- Original Message -
From: Paul Michali
it not implemented. This
way, you simply check for the feature set required.
Best Regards,
Solly Ross
- Original Message -
From: Nikunj Aggarwal nikunj.aggar...@hp.com
To: openstack-dev@lists.openstack.org
Sent: Tuesday, October 14, 2014 4:53:42 AM
Subject: [openstack-dev] [horizon]Blueprint
Sure, feel free to put my response in the Blueprint page. Thanks for the quick
answer.
Best Regards,
Solly Ross
- Original Message -
From: Nikunj Aggarwal nikunj.aggar...@hp.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Cc
I'm in favor of killing Python 2.6 with fire.
Honestly, I think it's hurting code readability and productivity --
You have to constantly think about whether or not some feature that
the rest of the universe is already using is supported in Python 2.6
whenever you write code.
As for readability,
The reason it was bounded was because we (the websockify upstream mantainers)
made a backwards-incompatible change (for good reasons -- it brought websockify
more inline with the Python standard library interfaces).
However, OpenStack had subclassed the WebSocketProxy code, and so the change
Monty, your messages are always super-entertaining to read.
They also generally have very good points, which is an added bonus :-P
- Original Message -
From: Monty Taylor mord...@inaugust.com
To: OpenStack Development Mailing List (not for usage questions)
Overall, this looks good.
Your alternate implementation misses LVM support, and leaves an unused file
behind in the instance directory. Other than that, it's acceptable for a
late-stage change, IMO.
Best Regards,
Solly
- Original Message -
From: Michael Still mi...@stillhq.com
To:
for websockify
On 09/22/2014 02:58 PM, Solly Ross wrote:
The reason it was bounded was because we (the websockify upstream
mantainers) made a backwards-incompatible change (for good reasons -- it
brought websockify more inline with the Python standard library
interfaces).
However
was
here: http://lists.openstack.org/pipermail/openstack-dev/2014-April/031689.html,
which basically reiterates what David says above (it's good to have links to the
past discussions, IMO).
Best Regards,
Solly Ross
P.S. Here's hoping that the JSHint devs eventually find a way to remove that
line
Thanks! ESLint looks interesting. I'm curious to see what it
says about the Horizon source. I'll keep it in mind for future
personal projects and the like.
Best Regards,
Solly Ross
- Original Message -
From: Martin Geisler mar...@geisler.net
To: OpenStack Development Mailing List
they tried to create a node.
Best Regards,
Solly Ross
- Original Message -
From: Sean Dague s...@dague.net
To: openstack-dev@lists.openstack.org
Sent: Wednesday, September 10, 2014 10:33:05 AM
Subject: Re: [openstack-dev] On an API proxy from baremetal to ironic
On 09/09/2014 11:22 PM
JSHint *isn't* Douglas Crockford. It was written by someone who
(understandably)
thought Douglas Crockford had some good ideas, but was overzealous. It does
mostly the
same things, but is more lenient with regards to style elements.
The license is as such:
in
build
On 2014-09-10 13:00:29 -0400 (-0400), Solly Ross wrote:
JSHint *isn't* Douglas Crockford. It was written by someone who
(understandably) thought Douglas Crockford had some good ideas,
but was overzealous.
[...]
Overzealous enough to copy his code.
?? This sentence doesn't make
think it's
safe to just tell people to install it from other sources (pip install) until
we can get the package into Fedora.
Best Regards,
Solly Ross
- Original Message -
From: Matt Riedemann mrie...@linux.vnet.ibm.com
To: OpenStack Development Mailing List (not for usage questions
? If nobody's using it, or the people using it aren't
using in an
extensive fashion, I think we don't need to make a proxy for it. Strengthening
this
argument is the fact that we would only be proxying the first two calls, so it
wouldn't
be a drop-in replacement anyway.
Best Regards,
Solly Ross
On Fri, Sep 5, 2014 at 4:05 AM, Nikola Đipanov ndipa...@redhat.com wrote:
On 09/04/2014 10:25 PM, Solly Ross wrote:
Anyway, I think it would be useful to have some sort of page where people
could say I'm an SME in X, ask me for reviews and then patch submitters
could go
and say, oh, I
the
pool is file-based and automatically created in the same location as the
current image
cache, there is little risk associated.
Best Regards,
Solly Ross
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
degree
(if he or she can, then he or she should be a libvirt core as well).
A strong +1 to Dan's proposal. I think this would also make it easier for
non-core reviewers to get started reviewing, without having a specialized tool
setup.
Best Regards,
Solly Ross
P.S.
This is a crisis. A large
implements a framework
for authenticating
and encrypting communication between the VNC proxy and the actual compute
nodes, and then
implements a TLS/x509 driver using that framework.
The patches don't touch much, and are enabled optionally, so they should be
relatively safe.
Best Regards,
Solly Ross
(see comments inline)
- Original Message -
From: Jay Pipes jaypi...@gmail.com
To: openstack-dev@lists.openstack.org
Sent: Thursday, September 4, 2014 2:34:28 PM
Subject: Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno
On 09/03/2014 11:57 AM, Solly Ross wrote
of patches, and thus
less of a
sudden influx of patches in the couple weeks before feature proposal freeze.
Best Regards,
Solly Ross
- Original Message -
From: Nikola Đipanov ndipa...@redhat.com
To: openstack-dev@lists.openstack.org
Sent: Wednesday, September 3, 2014 5:50:09 AM
Subject
(response inline)
- Original Message -
From: Daniel P. Berrange berra...@redhat.com
To: Solly Ross sr...@redhat.com
Cc: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, August 21, 2014 11:23:17 AM
Subject: Re: [openstack
to
libvirt in unit tests
On 8/11/2014 4:42 AM, Daniel P. Berrange wrote:
On Mon, Aug 04, 2014 at 06:46:13PM -0400, Solly Ross wrote:
Hi,
I was wondering if there was a way to get a non-readonly connection
to libvirt when running the unit tests
on the CI. If I call `LibvirtDriver
want
to run OpenStack on an older platform, then you'll need to run an older
OpenStack or backport the required
packages.
Best Regards,
Solly Ross
- Original Message -
From: Joe Gordon joe.gord...@gmail.com
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Sent
Regards,
Solly Ross
- Original Message -
From: Chen CH Ji jiche...@cn.ibm.com
To: openstack-dev@lists.openstack.org
Sent: Friday, August 1, 2014 5:04:16 AM
Subject: [openstack-dev] [nova] libvirtError: XML error: Missing CPU model
name on 2nd level vm
Hi
I don't have a real PC to so
against a real target.
The tests in question are part of https://review.openstack.org/#/c/111459/,
and involve manipulating directory-based libvirt storage pools.
Best Regards,
Solly Ross
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
driver
use that. This seems to me to be the better option, since it means that when
the Baremetal driver is removed, the old ImageCacheManager
code goes with it, without someone having to manually remove it.
What do you think?
Best Regards,
Solly Ross
It was recommended I cross-post this for visibility.
Devs are welcome to provide feedback as well ;-)
Best Regards,
Solly Ross
- Forwarded Message -
From: Solly Ross sr...@redhat.com
To: openstack-operat...@lists.openstack.org
Sent: Tuesday, June 24, 2014 1:29:15 PM
Subject: Browser
.
Those poor people using IE 7...
Best Regards,
Solly Ross
- Original Message -
From: Anne Gentle a...@openstack.org
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, June 26, 2014 11:05:58 AM
Subject: Re: [openstack-dev
Hi Deepak,
This mailing list is for development discussions only. Please use the general
or operators
mailing list
(http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators) to
ask questions about running OpenStack.
Best Regards,
Solly Ross
- Original Message -
From
would simply be a sum of distances between
the individual
resources for the target and flavor.
Best Regards,
Solly Ross
Alex
From: Day, Phil philip@hp.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date: 06/06/2014 12:38
se. Instead (in general), we
have
sqlalchemy models which are then saved (which handles inserting, etc). So the
path
is api wrapper (the file you linked to) -- sqlalchemy api implementation --
sqlalchemy
model.
Hope this helps.
Best Regards,
Solly Ross
- Original Message -
From: Rad
...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, May 8, 2014 5:08:32 AM
Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation
through Heat (pt.2)
On Mon, May 05, 2014 at 01:40:43PM -0400, Solly
P.S. I feel like this is something that should be discussed at the design
summit. Perhaps there's an existing session this could be discussed in (the
unsession, perhaps?)
- Original Message -
From: Solly Ross sr...@redhat.com
To: Daniel P. Berrange berra...@redhat.com, OpenStack
(response inline)
- Original Message -
From: Zane Bitter zbit...@redhat.com
To: openstack-dev@lists.openstack.org
Sent: Tuesday, May 6, 2014 9:09:09 PM
Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation
through Heat (pt.2)
On 05/05/14 13:40, Solly Ross wrote
than that, you could have someone specify
that they wanted 1.34GB of RAM, for instance, and then you have
all sorts of weird stuff going on).
Best Regards,
Solly Ross
- Original Message -
From: Dimitri Mazmanov dimitri.mazma...@ericsson.com
To: OpenStack Development Mailing List
-allocated).
Best Regards,
Solly Ross
- Original Message -
From: Serg Melikyan smelik...@mirantis.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, May 5, 2014 2:18:21 AM
Subject: Re: [openstack-dev] [Nova][Heat] Custom Nova
a problem dealing with a choice between 64
(or even 512) different flavors, perhaps it's time to upgrade :-P.
Best Regards,
Solly Ross
- Original Message -
From: Clint Byrum cl...@fewbar.com
To: openstack-dev openstack-dev@lists.openstack.org
Sent: Monday, May 5, 2014 12:28:58 PM
Subject
RAM to only 2GB, 4GB, or 16GB), but you avoid
exponential flavor explosion by separating out the axes.
Best Regards,
Solly Ross
P.S. For people who use flavor names to convey information about the
workload, that probably a job better done by the VM tagging proposal
(https://review.openstack.org
websockify 0.6
on pypi.openstack.org? If that
process involves updating global-requirements, there's a follow up question:
since websockify 0.6 breaks backwards
compatibility, what happens in between the time that global-requirements gets
updated and the related change gets
pushed?
Best Regards,
Solly
Just FYI, you'll see a lot of people refer to `git blame`. They're basically
the same
command.
Best Regards,
Solly Ross
- Original Message -
From: Sean Dague s...@dague.net
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent
tailoring the operation to the quirks of the
particular drivers.
Best Regards,
Solly Ross
- Original Message -
From: Christopher Lefelhocz christopher.lefel...@rackspace.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday
of times (i.e. it won't time out).
Best Regards,
Solly Ross
- Original Message -
From: Gareth academicgar...@gmail.com
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Sent: Thursday, April 24, 2014 5:42:06 AM
Subject: [openstack-dev] [OpenStack][Nova] infinite attempts
have to write, since libvirt already
has a (limitted) storage driver for sheepdog (see the BP here:
https://review.openstack.org/#/c/86947/)
Best Regards,
Solly Ross
- Original Message -
From: Scott Devoid dev...@anl.gov
To: OpenStack Development Mailing List openstack-dev
could also take a look at Oslo -- it's component-agnostic and the different
parts tend to
be a bit smaller than the other components.
Hope this helps, and good luck! We're always glad to have new contributors!
Best Regards,
Solly Ross
- Original Message -
From: Mayur Patil ram.nath241
frustrating. While you come to anticipate certain changes, IMHO it's
definitely much better to decide
on the design *before* you start coding, that way code reviews can focus on the
code, and you don't have
to completely rewrite patches as much.
Best Regards,
Solly Ross
- Original Message
. Something like that would be
problematic, as
blueprints could be proposed after summit.
Hope that helps. IMHO, the nova-specs gerrit repository is a great way to
review
blueprints. I'm really liking it so far.
Best Regards,
Solly Ross
- Original Message -
From: Kyle Mestery mest
, rabbit_hosts and
rabbit_password)
- notification_driver = messaging
Hopefully this is helpful, as some of these options are not set by default in
devstack.
Best Regards,
Solly Ross
- Original Message -
From: Nader Lahouti nader.laho...@gmail.com
To: OpenStack Development Mailing List openstack
the timeout based on image size, network conditions, etc, or we
should just remove the shortcut
entirely, and just have people do the two steps separately (the current
workaround for large disk images).
Best Regards,
Solly Ross
- Original Message -
From: Ben Swartzlander ben.swartzlan
Is there a blueprint for using this for Cinder-Nova interaction?
Best Regards,
Solly Ross
- Original Message -
From: Mike Perez thin...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, April 8, 2014 3:58:31 PM
, etc.
Best Regards,
Solly Ross
- Original Message -
From: Matthew Booth mbo...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, April 7, 2014 10:47:35 AM
Subject: Re: [openstack-dev] [OpenStack-Dev][Nova][VMWare
Simon, please use the operators list or general list for questions such as this
in the future.
https://wiki.openstack.org/wiki/Mailing_Lists#General_List
Best Regards,
Solly Ross
- Original Message -
From: Xu (Simon) Chen xche...@gmail.com
To: openstack-dev@lists.openstack.org
Sent
I just wanted to add that if you modify code, you can commit it into a
temporary commit,
and that will be preserved.
Best Regards,
Solly Ross
- Original Message -
From: Dolph Mathews dolph.math...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev
IMHO, having Example: on a separate line from the actual option is a lot
easier for humans:
you just delete a single character or use your editor-of-choice's uncomment
macro to activate
a line.
- Original Message -
From: Russell Bryant rbry...@redhat.com
To:
to OpenStack Macaroni. The vote should probably be held after OpenStack Summit,
so that we can discuss the potential name change in a Summit session.
Best Regards,
Solly Ross
P.S. Happy April Fools Day!
___
OpenStack-dev mailing list
OpenStack-dev
was
already VMWare-specific.
Best Regards,
Solly Ross
- Original Message -
From: Jay Lau jay.lau@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, March 31, 2014 10:36:17 AM
Subject: Re: [openstack-dev] [OpenStack-Dev
(db_regexp_op)(
str(filters[filter_name]))`)?
Best Regards,
Solly Ross
- Original Message -
From: Chris Friesen chris.frie...@windriver.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, March
I should specify that I meant updating the OS version used by the CI.
- Original Message -
From: Solly Ross sr...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, March 31, 2014 5:24:12 PM
Subject: Re: [openstack
There was some talk about updating the CI for Juno.
Has this been done/when will this be done?
Best Regards,
Solly Ross
- Original Message -
From: Russell Bryant rbry...@redhat.com
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Sent: Monday, March 31, 2014 2:23
Hi Shiva,
This list is for development discussion and questions only. Please use the
Operator List
(http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators)
or the general list for questions about deploying or operating OpenStack.
Best Regards,
Solly Ross
- Original
there's a lower bound in the 1.x
range, just not an upper bound).
Best Regards,
Solly Ross
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
:30 AM, Solly Ross wrote:
Hi,
I currently have a patch up for review
(https://review.openstack.org/#/c/81373/) to limit psutil be 2.0.0.
2.0.0 just came out a couple weeks ago, and breaks the API in a major way.
Until we can port our code to the
latest version, I suggest we limit
What bug tracker should I file under? I tried filing one under the openstack
common infrastructure tracker,
but was told that it wasn't the correct place to file such a bug.
Best Regards,
Solly Ross
- Original Message -
From: Sean Dague s...@dague.net
To: OpenStack Development Mailing
: Re: [openstack-dev] [depfreeze] Exception: limit psutil to 2.0.0
On Wed, Mar 26, 2014 at 12:32 PM, Solly Ross sr...@redhat.com wrote:
What bug tracker should I file under? I tried filing one under the openstack
common infrastructure tracker,
but was told that it wasn't the correct place
a
connection.
Best Regards,
Solly Ross
- Original Message -
From: Chris Friesen chris.frie...@windriver.com
To: openstack-dev@lists.openstack.org
Sent: Thursday, March 20, 2014 2:59:55 PM
Subject: Re: [openstack-dev] [nova] instances stuck with task_state of
REBOOTING
On 03/20/2014 12:29 PM
, whereas people using
versioned releases are less likely to be as flexible.
Best Regards,
Solly Ross
- Original Message -
From: Thierry Carrez thie...@openstack.org
To: openstack-dev@lists.openstack.org
Sent: Thursday, March 20, 2014 6:51:26 AM
Subject: Re: [openstack-dev] [nova] Backwards
to trivial changes that will be a burden on the
people who need
to approve changes and will distract from substantial changes (changes to the
design parts
of the blueprint, etc).
Best Regards,
Solly Ross
- Original Message -
From: Russell Bryant rbry...@redhat.com
To: OpenStack Development
Hi Chris,
Are you in the position to determine whether or not this happens with the
latest master code?
Either way, it definitely looks like a bug.
If you could give more specific reproduction instructions, that would be most
useful.
Best Regards,
Solly Ross
- Original Message -
From
Sorry if my meaning was unclear. I think we should revert as well.
Best Regards,
Solly Ross
- Original Message -
From: David Kranz dkr...@redhat.com
To: openstack-dev@lists.openstack.org
Sent: Thursday, March 20, 2014 2:20:42 PM
Subject: Re: [openstack-dev] [nova] Backwards incompatible
, we need to ensure that we *can* test code that uses
features present in later versions of libvirt. 0.9.8 came out over two years
ago making it fairly old. I think it's important to keep up-to-date on what
versions we test with.
Best Regards,
Solly Ross
- Original Message -
From
.
Best Regards,
Solly Ross
- Original Message -
From: Chris Behrens cbehr...@codestud.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, March 18, 2014 3:25:08 PM
Subject: Re: [openstack-dev] Constructive Conversations
I've also had devstack somehow end up starting qpid, then try to start rabbit
on F20. In this case
it seems sufficient to stop qpid then re-run devstack. I haven't had time to
track down the issue yet.
Best Regards,
Solly Ross
- Original Message -
From: John Eckersberg jecke
).
Although in the case of updating a library that you wrote, it's less likely to
break things.
Best Regards,
Solly Ross
- Original Message -
From: Ben Nemec openst...@nemebean.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Cc: Solly Ross
to
openstack-common.conf
IMHO, update.py needs a bit of work (well, I think the whole code copying thing
needs a bit of work, but that's a different story).
Best Regards,
Solly Ross
- Original Message -
From: Jay S Bryant jsbry...@us.ibm.com
To: OpenStack Development Mailing List (not for usage
libraries on the
dependency chart first, so that any graduated libraries
will have olso.xyz dependencies, and not code-sync dependencies.
Best Regards,
Solly Ross
- Original Message -
From: Jay S Bryant jsbry...@us.ibm.com
To: OpenStack Development Mailing List (not for usage questions
projects that use
noVNC, so we'd need to make sure that no OpenStack-specific code gets merged
into noVNC if we adopt it. Other that that, though, adopting noVNC doesn't
sound like a horrible idea.
Best Regards,
Solly Ross
- Original Message -
From: Ben Nemec openst...@nemebean.com
of the
current stack traces of threads and green threads, as well as the current
configuration options, will be dumped.
It doesn't look like exactly what you want, but I figured it might be useful to
you anyway.
Best Regards,
Solly Ross
- Original Message -
From: Chris Friesen chris.frie
@Monty: having a packaging system sounds like a good idea. Send us a pull
request on github.com/kanaka/noVNC.
Best Regards,
Solly Ross
- Original Message -
From: Monty Taylor mord...@inaugust.com
To: Sean Dague s...@dague.net, OpenStack Development Mailing List (not for
usage
Has anyone tried compiling rootwrap under Cython? Even with non-optimized
libraries,
Cython sometimes sees speedups.
Best Regards,
Solly Ross
- Original Message -
From: Vishvananda Ishaya vishvana...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack
Websockify Release
On 02/27/2014 11:22 AM, Thierry Carrez wrote:
Solly Ross wrote:
We (the websockify/noVNC team) have released a new version of websockify
(0.6.0). It contains several fixes and features relating to OpenStack (a
couple of bugs were fixed, and native support for the `logging
for updating Nova to work with
the new version?
Best Regards,
Solly Ross
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
1 - 100 of 107 matches
Mail list logo
