openstack-dev] [nova][libvirt] Non-readonly connection 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
nection to
> libvirt in unit tests
>
> On Thu, Aug 21, 2014 at 10:52:42AM -0400, Solly Ross wrote:
> > FYI, the context of this is that I would like to be able to test some
> > of the libvirt storage pool code against a live file system, as we
> > currently test the storage po
(response inline)
- Original Message -
> From: "Daniel P. Berrange"
> To: "Solly Ross"
> Cc: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Thursday, August 21, 2014 11:23:17 AM
> Subject: Re: [openstack
it seemed that
a lot
of specs didn't get approved until spec freeze. Perhaps if we had more
staggered
approval of specs, we'd have more staggered submission of patches, and thus
less of a
sudden influx of patches in the couple weeks before feature proposal freeze.
Best Regards,
Solly
but most likely cannot provide the latter to a sufficient 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 specia
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
(see comments inline)
- Original Message -
> From: "Jay Pipes"
> 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, S
>
>
> 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 m
pool to manage its images.
Since 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
u're not using RDO I 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"
> To: "OpenStack Development Mailing
ve fashion? 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 replacemen
r that something broke because they tried to create a node.
Best Regards,
Solly Ross
- Original Message -
> From: "Sean Dague"
> To: openstack-dev@lists.openstack.org
> Sent: Wednesday, September 10, 2014 10:33:05 AM
> Subject: Re: [openstack-dev] On an API proxy
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: https://github.com/jshint/jshint/blob
uild
>
> 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
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
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"
> To: "OpenStack Developm
ich case
rsync would connect via the daemon and not ssh). Is it worth it?
Additionally, if we do not eliminate number 3, is it worth it to refactor the
code to eliminate numbers 2 and 4 (I already have code
to eliminate number 1 -- see https://gist.github.com/DirectXMan12/9217699).
Best Regards,
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
ase
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 fo
Good idea -- here's the blueprint:
https://blueprints.launchpad.net/nova/+spec/update-to-latest-websockify
- Original Message -
From: "Solly Ross"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Wednesday, February 26, 2014 11:55:25 A
quickly, since I've been working on
the related code recently.
Best Regards,
Solly Ross
- Original Message -
> From: "Vishvananda Ishaya"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, November 18, 2014 4:07
Whoops, that should say "assertions" not "exceptions".
- Original Message -
> From: "Solly Ross"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Monday, November 24, 2014 12:00:44 AM
> Subject
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"
> To: "OpenStack Dev
etup for the XYZ app", you 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"
> To: openstack-dev@lists.ope
> I can't comment on other projects, but Nova definitely needs the soft
> delete in the main nova database. Perhaps not for every table, but
> there is definitely code in the code base which uses it right now.
> Search for read_deleted=True if you're curious.
Just to save people a bit of time, it'
gt; 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
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ave a spec or some code, I'd be happy to give some feedback,
if you'd like (post it on Gerrit as WIP, or something like that).
Best Regards,
Solly Ross
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
,
pressing escape can be accidental (either through habit or through accidentally
pressing the key).
Best Regards,
Solly Ross
- Original Message -
> From: "Aaron Sahlin"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Thursday, D
ble to place the releases so that
devstack
can install them?
Best Regards,
Solly Ross
__
OpenStack Development Mailing List (not for usage quest
> 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
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"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Thursday, April 24
still tailoring the operation to the quirks of the
particular drivers.
Best Regards,
Solly Ross
- Original Message -
From: "Christopher Lefelhocz"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Thursday, April 24, 2014 11:17:41 AM
Subject:
times (i.e. it won't time out).
Best Regards,
Solly Ross
- Original Message -
From: "Gareth"
To: "OpenStack Development Mailing List"
Sent: Thursday, April 24, 2014 5:42:06 AM
Subject: [openstack-dev] [OpenStack][Nova] infinite attempts left
When run "nova-
tting 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 Rega
s that are extremely over-allocated).
Best Regards,
Solly Ross
- Original Message -
From: "Serg Melikyan"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, May 5, 2014 2:18:21 AM
Subject: Re: [openstack-dev] [Nova][Heat] Custom Nova F
if your computer has 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"
To: "openstack-dev"
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
M has
even more granularity 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"
To: "OpenStack Development Mailing List (no
(response inline)
- Original Message -
> From: "Zane Bitter"
> 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 1
Daniel P. Berrange"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> 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:
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"
> To: "Daniel P. Berrange" , "OpenSt
table" per 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,
Sol
ting flavors that couldn't fit the
target
configuration. The "distance" score would simply be a sum of distances between
the individual
resources for the target and flavor.
Best Regards,
Solly Ross
>
> Alex
>
>
>
>
> From: "Day, Phil"
> To
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 -
> F
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"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent
hat there are a few other 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: &quo
week before last, and
I'll start the discussion about a new release of noVNC.
Best Regards,
Solly Ross
- Original Message -
From: "Sean Dague"
To: "OpenStack Development Mailing List (not for usage questions)"
, openst...@nemebean.com
Cc: openstack-in...@lists.opens
f 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: "Chr
@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"
To: "Sean Dague" , "OpenStack Development Mailing List (not for
usage questions)&
.conf to revert the changes 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"
To: "OpenStack Developm
e the "lowest" 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"
To: "OpenStack Development Mailing List (no
(not meant to
sound snarky).
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"
To: "OpenStack Development Mailing List (not for usage questions)"
Cc:
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 Eckersber
bvirt, 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
penStack (I've never actually
had that many resources, probably since I'm a developer and not a deployer),
I've definitely
used a similar workflow with other applications which supported pagination via
offset. I definitely
think it could be a useful feature.
Best Regards,
Solly Ross
e cases are
dwarfed by the aforementioned cases.
Just my 0.3 BTC.
Best Regards,
Solly Ross
- Original Message -
From: "Chris Behrens"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Tuesday, March 18, 2014 3:25:08 PM
Subject: Re: [ope
o to speak, whereas people using
versioned releases are less likely to be as flexible.
Best Regards,
Solly Ross
- Original Message -
From: "Thierry Carrez"
To: openstack-dev@lists.openstack.org
Sent: Thursday, March 20, 2014 6:51:26 AM
Subject: Re: [openstack-dev] [nova] Backwa
e, etc) will lead 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: "Russel
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"
To: openstack-dev@lists.openstack.org
Sent: Thursday, March 20, 2014 2:20:42 PM
Subject: Re: [openstack-dev] [nova] Backwards incompatible A
we have a
connection.
Best Regards,
Solly Ross
- Original Message -
From: "Chris Friesen"
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,
tly
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
Regards,
Solly Ross
- Original Message -
From: "Sean Dague"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Wednesday, March 26, 2014 10:39:41 AM
Subject: Re: [openstack-dev] [depfreeze] Exception: limit psutil to <2.0.0
On 03/26/2014
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"
To: "OpenStack Developme
pfreeze] Exception: limit psutil to <2.0.0
On Wed, Mar 26, 2014 at 12:32 PM, Solly Ross 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 to file such a bug.
>
&g
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
re the code was
already VMWare-specific.
Best Regards,
Solly Ross
- Original Message -
From: "Jay Lau"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, March 31, 2014 10:36:17 AM
Subject: Re: [openstack-dev] [OpenStack-Dev][Nova][VMWare] E
(db_regexp_op)(
str(filters[filter_name]))`)?
Best Regards,
Solly Ross
- Original Message -
From: "Chris Friesen"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, March 31, 2014 10:57:04 AM
Subject: Re: [
I should specify that I meant updating the OS version used by the CI.
- Original Message -
From: "Solly Ross"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, March 31, 2014 5:24:12 PM
Subject: Re: [openstack-dev] [Nova] Juno open fo
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"
To: "OpenStack Development Mailing List"
Sent: Monday, March 31, 2014 2:23:32 PM
Subject: [openstack-d
k Marconi project
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 mailin
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"
To: openstack-dev@lists.openstack.org
Sent: Wed
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"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Thurs
low tuning to individual cores, etc.
Best Regards,
Solly Ross
- Original Message -
From: "Matthew Booth"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, April 7, 2014 10:47:35 AM
Subject: Re: [openstack-dev] [OpenStack-Dev][Nova][VM
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"
To: openstack-dev@lists.openstack.org
Sent: Saturda
ons (e.g. for rabbit, 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"
To: "OpenStack Development Ma
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
Is there a blueprint for using this for Cinder-Nova interaction?
Best Regards,
Solly Ross
- Original Message -
From: "Mike Perez"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Tuesday, April 8, 2014 3:58:31 PM
Subject: Re: [openstac
is fairly
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
--
to have a summit session. 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
Additionally, storing lots of binary blobs in a Git repo is sub-optimal,
as the repo size ballons very quickly. Storing images on the Wiki, or
elsewhere that has stable image hosting, is a much better solution, IMHO
(but try asciiflow or asciiflow traditional first!).
Best Regards,
Solly Ross
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: "M
t you 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"
To: "OpenStack Development Mailing List"
Sent: Monda
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, t
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
wou
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"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Friday, September 19, 2014 9:52:4
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"
> To: "OpenStack Dev
> exception 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 Pyt
ack-dev
>
> --
> Pasquale Porreca
>
> DEK Technologies
> Via dei Castelli Romani, 22
> 00040 Pomezia (Roma)
>
> Mobile +39 3394823805
> Skype paskporr
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Best Regards,
Solly Ross
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Modernizr and then warn if the requisite feature set it not implemented. This
way, you simply check for the feature set required.
Best Regards,
Solly Ross
- Original Message -
> From: "Nikunj Aggarwal"
> To: openstack-dev@lists.openstack.org
> Sent: Tuesday, Octob
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"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Cc: sr...@redhat
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: "
l-data", "images" and
"critical-data" might be stored on specially-tuned high-performance backends,
while "critical-data" might be on a large general-purpose backend.
Best Regards,
Solly Ross
- Original Message -
> From: "Alexander Tivelkov&qu
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 o
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"
> To: "OpenStack Development Mailing List (not for us
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
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"
To: openstack-operat...@lists.openstack.org
Sent: Tuesday, June 24, 2014 1:29:15 PM
Subject: Browser Usage
stics.
Those poor people using IE 7...
Best Regards,
Solly Ross
- Original Message -
> From: "Anne Gentle"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Thursday, June 26, 2014 11:05:58 AM
> Subject: Re: [openstack-dev]
run some of the tests 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 lis
Baremetal 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,
1 - 100 of 120 matches
Mail list logo
