this point.
Thanks,
[1] https://blueprints.launchpad.net/nova/+spec/deprecate-nova-network
--
Russell Bryant
Nova PTL
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpa
On 03/20/2013 04:43 PM, Lorin Hochstein wrote:
> iptables -D POSTROUTING -t mangle -p udp --dport 68 -j CHECKSUM
> --checksum-fill
Are you *sure* this rule was applied to the traffic in question? It
really sounds like you were hitting this issue ...
--
Russell
=2013-0335
https://bugs.launchpad.net/nova/+bug/1125378
- --
Russell Bryant
OpenStack Vulnerability Management Team
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net
ed (trusted network, encryption).
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
nt that patches for vulnerabilities are
complete and that getting them merged on release day should not run into
unexpected problems.
Thank you,
- --
Russell Bryant
OpenStack Vulnerability Management Team
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with
-09 - Errata 1
- Updated to reflect that the v2 API in Folsom and Grizzly was also
affected
- Include links to fixes for the v2 API
- Added CVE-2012-5482 for the vulnerability against the v2 API
2012-11-07 - Original Version
- --
Russell Bryant
OpenStack Vulnerability Management Team
On 11/07/2012 05:09 PM, Russell Bryant wrote:
> OpenStack Security Advisory: 2012-017
> CVE: CVE-2012-4573
> Date: November 7, 2012
> Title: Authentication bypass for image deletion
> Impact: High
> Reporter: Gabe Westmaas (Rackspace)
> Products: Glance
> Affects
Greetings,
The organizers of the Cloud devroom at FOSDEM 2012 invite you to submit
a session proposal. The purpose of this devroom is to serve as a
meeting point for cloud infrastructure projects, including a unique
opportunity for discussion and collaboration between developers from
different pr
://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-4573
https://bugs.launchpad.net/glance/+bug/1065187
Notes:
This fix will be included in the grizzly-1 development milestone and in
a future 2012.2 (Folsom) release.
--
Russell Bryant
OpenStack Vulnerability Management Team
gt; Thanks in advance.
This is an LVM issue that isn't specific to OpenStack. I would do some
reading on the topic to gain a better understanding of LVM...
If you're just doing basic testing, you can use this little hack:
$ sudo truncate --size 20G ~/nova-volumes
$ sudo losetup -
Signing up for a new mailing list for every new
development effort would be a nightmare to keep up with. I *really,
really* think the list should be dropped and all discussions should be
on openstack-dev.
--
Russell Bryant
___
Mailing list: https:/
just to keep informed on design discussions. That will avoid the
> subgroup coming up with a design that will be rejected by the larger
> group once it is submitted there.
>
> Why not use a subject prefix instead ? Like [baremetal] ?
A huge +1.
--
Russell Bryant
_
On 10/25/2012 09:30 PM, Michael Still wrote:
> On 10/26/2012 12:24 PM, Russell Bryant wrote:
>> On 10/25/2012 08:18 PM, Michael Still wrote:
>>> I'd be interested in comments people might have. The code is at
>>> http://bazaar.launchpad.net/~mikalstill/+junk/openst
cases where
the reporter == triager. Developers filing bugs and triaging them for
their own patches shouldn't be counted.
You should move this to github so I can send you a pull request. :-)
--
Russell Bryant
___
Mailing list: https://launchpa
ck_EPEL
You can also follow some of our instructions for the Fedora test day,
which included testing out Cinder:
https://fedoraproject.org/wiki/Test_Day:2012-09-18_OpenStack
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Po
sidered stable or even usable until this exists.
I think that's a bit strong and not accurate. To be more specific,
there is no stable API *in OpenStack* for consuming notifications. It's
certainly possible to consume them. That is the whole point.
it log for
nova/volumes/.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
/openstack/keystone/commit/24df3adb3f50cbb5ada411bc67aba8a781e6a431
References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-4456
https://bugs.launchpad.net/keystone/+bug/1006815
https://bugs.launchpad.net/keystone/+bug/1006822
- --
Russell Bryant
OpenStack Vulnerability Management Team
http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-4457
https://bugs.launchpad.net/keystone/+bug/988920
--
Russell Bryant
OpenStack Vulnerability Management Team
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpa
You can run multiple instances of nova-scheduler to scale it out, and it
doesn't matter which one processes each scheduler request.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
U
ions for me?
There was a lively debate about this back when the LESS support was
merged. The compromise was that we would work with the Horizon
developers on shipping a compiled stylesheet in our package. As for the
detailed mechanics of doing so, I don't know. :-)
https://lists.launchpad.net
.html
Thank you!
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
ing to make it in for
Folsom. In addition to working through the technical details, it also
desperately needs some documentation (ideally both architectural, as
well as how to use it).
It seems like we should be able to get this all wrapped up for Grizzly,
though.
--
Russell Bryant
__
ption Bs, the simplicity of option C is most appealing to me.
+1
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
like the simple group of openstack@, openstack-dev@, and
openstack-announce@.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstac
for some other problems around token
expiration, though.
For reference: https://lists.launchpad.net/openstack/msg15164.html
- --
Russell Bryant
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enig
ot; projects into a single devroom, if need be.
>
> Thoughts ? Also if you want to help organize, please let me know.
Sounds like a great idea to me! I'm also happy to help organize.
--
Russell Bryant
___
Mailing list: https://launchp
ture Essex (2012.1) release.
- --
Russell Bryant
OpenStack Vulnerability Management Team
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlA/iZEACgkQFg9ft4s9SAZ0zQCeKEqxWbDFum/f6l00H0x6FL2L
QEEA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This advisory included the wrong CVE. It was CVE-2012-3540. Sorry
about that.
On 08/30/2012 11:10 AM, Russell Bryant wrote:
> OpenStack Security Advisory: 2012-012 CVE: CVE-2012-3542
This should have been CVE-2012-3540
> Date: August 30
included in a future Essex (2012.1) release.
- --
Russell Bryant
OpenStack Vulnerability Management Team
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlA/glMACgkQFg9ft4s9SAYMLACfdRBa
and whatever changes need to be made, can be
> made.
I'm not talking about all configuration options. I'm talking about this
single configuration option. Existing installations that did not
specify rpc_backend because they did not need to will break if the
default is changed.
--
default that doesn't work for
anyone makes any sense.
> * The RPC code is now in openstack-common, so addressing this later will only
> create additional technical debt.
I don't feel that it's something that ever *needs* to be addressed, so
it's not techni
hese changes into nova? It seems that nova has a
> copy-paste of openstack-common inside it, should I just mirror the
> changes to nova once they're accepted in openstack-common?
>
> I'm cc'ing Russell Bryant because he originally created the
> openstack-common module.
broker you are
using. If the Qpid broker was running, but nova was configured to use
impl_kombu, I would not expect it to work. Once nova was configured to
use the right driver for this setup (impl_qpid), it worked, so I don't
think there are any bugs here.
s://review.openstack.org/#/dashboard/1711
+1
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
penstack.org/#/dashboard/1812
+1 !
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
n, which I apoligize
> in advance for :)
>
> Sent from my digital shackles.
>
> [1] https://github.com/hub-cap/reddwarf_lite
> [2] https://github.com/platformlayer/platformlayer
> [3] http://heat-api.org/
Check out OpenShift Origin:
https://openshift.redhat.com/c
patch that did the update. There were some
> files missing. I'll try and check.
Ok, it was probably just a failure to 'git add' everything. However, if
you guys discover a problem with update.py not copying everything,
please report it against openstack-common so we can fix it
27;t think I understand your question. If you add "rpc" to
openstack-common.conf, and then run the update.py tool in
openstack-common, it should pull in everything.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Pos
new merge.
> D. Such patches require the same justification and scrutiny as any
> other standard project patch.
This all seems fine to me.
> Please discuss! If we're able to reach general agreement about this
> process, I will document the process in the openstac
nova/openstack/common/rpc/proxy.py
Here is one of the simpler conversions:
https://github.com/openstack/nova/commit/f50ce35c9cf2e05d205485586da1cb6d5433ba56
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : open
35:16
> nova-network os-host.int.seas.harvard.edu nova
> enabled:-) 2012-06-21 16:35:17
>
> Creating volumes works just fine.
The timeout occurs when nova-compute is trying to do an rpc call to
nova-volume. It looks like this is just the compute log.
ersight in impl_qpid. I'll get it fixed.
Thanks for pointing it out!
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
/bbdf82c5ec3e31a5dc43948291c4f37ce1098714
Essex:
https://github.com/openstack/nova/commit/3ee026e4252cd4140b50675e857695b195ab5065
Diablo: https://review.openstack.org/#/c/8239/
Thanks,
--
Russell Bryant
OpenStack Vulnerability Management Team
On 06/06/2012 03:47 PM, Russell Bryant wrote:
> OpenStack Secur
ly shouldn't be used by any other applications.
In any case, this sounds like a reasonable improvement. Patches
welcome. :-)
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
On 06/06/2012 07:08 PM, James R Penick wrote:
> Hey Folks,
Check out: http://openstack.org/community/jobs/
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : ht
9beac2978
Diablo: https://review.openstack.org/#/c/8239/
Notes:
This fix will be included in the folsom-2 development milestone and in
future essex and diablo releases.
--
Russell Bryant
OpenStack Vulnerability Management Team
___
Mailing list: https://laun
rators and such...
Yes, if it is using run_as_root=True, then it has to be run with
nova-rootwrap.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
M
On 06/05/2012 05:35 PM, Russell Bryant wrote:
> On 06/05/2012 05:25 PM, Mark Washenberger wrote:
>>
>>
>> "Mark McLoughlin" said:
>>
>>> On Tue, 2012-06-05 at 12:21 -0400, Mark Washenberger wrote:
>>>>> http://wiki.openstack.org/Common
eady to propose, actually), but I have
other things I should work on after that.
How about the stakeholders interested in using this code in other
projects? Do you want the current code in now (with the likelihood of
having to adapt to some API changes later), or would you like to get
together and w
to me hypervisor agnostic but I'm not sure.
>
> Is there a command to know which hypervisor is being used by openstack?
If you followed those instructions, it instructs you to use libvirt+KVM.
--
Russell Bryant
___
Mailing list: https:/
lready copying
it (in a feature branch for Quantum, Cinder, the Heat project, at
least), so moving it as is will leave us in a better spot than we are now.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists
On 05/30/2012 03:54 AM, Alessandro Tagliapietra wrote:
> Thank you Russel, i'll wait for the fix
I attached a patch to this bug. Could you try it out?
> https://bugs.launchpad.net/nova/+bug/999698
--
Russell Bryant
___
Mailing
l cases. The bad thing is that we
would not be able to set the queue to be auto-deleted in this case, so
we could end up with a "leak" of unwanted message queues.
I'm tempted to just write a patch that does #1 for now to address the
immediate issue and then do something better late
from me. That seems like a pretty reasonable compromise.
(My team may attack me for that, too.)
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
next patch comes up.
What kind of timeline do you think that would be? Would it be after
Folsom? Maybe by then the state of Node.js packages will be in better
shape.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Pos
On 05/25/2012 04:00 PM, Stefano Maffulli wrote:
> On Fri 25 May 2012 11:03:40 AM PDT, Russell Bryant wrote:
>> We have been posting security advisories to the main mailing list.
>
> I'm interested to understand why you've done that. The announce list
> has always
eck them.
We have been posting security advisories to the main mailing list. I
worry that they get missed by a lot of pepole since it's such a high
volume list. Using the announce list would be great for those.
--
Russell Bryant
___
Mailing l
7;re talking about potential policy issues ... isn't
*everything* else server side in OpenStack Python? Is this going to
provide things that are hugely valuable that you really just can't
accomplish using Python?
--
Russell Bryant
___
Ma
tallation burden due to node not being easily available for all
platforms at present."
That would sure save us a lot of headaches if we could make that work. :-)
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to
Fedora (and EPEL for use
with RHEL and its derivatives).
https://bugzilla.redhat.com/show_bug.cgi?id=815018
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchp
y into the rpc code.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
his seems like a juju bug to me.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
t could be
that the instances were stopped, but it hadn't actually completed yet
when the request to delete the security groups came in. You have to
wait until the instances are gone before the security groups can be deleted.
--
Russell Bryant
eue at a time.
To be a bit pedantic, the result is that there is only one queue and two
consumers from that queue. Only one consumer gets each message. When
there is more than one consumer from the same queue, messages will be
distributed in a round-robin fashion.
--
Russell Bryant
___
the work of duplicating the
message as opposed to making nova send the message multiple times.
Perhaps using another exchange would make sense if it made ACLs easier
for ensuring that an application can only get notifications, and nothing
else on the nova exchange.
--
Rus
ioned
before, a topic exchange allows you to create a queue to get all
notifications or only notifications of a specific priority. If the
exchange type is changed to fanout, it's everybody gets everything, and
that's it.
--
Russell Bryant
___
Ma
et it up to receive all
notifications, or only notifications of a certain priority.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
f this API. It uses a connection pool behind the scenes.
You can search around through nova to find many uses of these functions.
Let me know if you have any questions!
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
ete the goal:
https://blueprints.launchpad.net/nova/+spec/no-db-compute
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : ht
On 05/07/2012 04:08 PM, Russell Bryant wrote:
> On 05/07/2012 03:40 PM, Doug Hellmann wrote:
>> The metering project will probably want to take advantage of this work.
>> How far along is it, and how can we help?
>
> I can speak to the nova.rpc part, at least.
>
> I
If anyone wants to take part of this, let me know so we don't duplicate
efforts.
Thanks,
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~open
future 2012.1 (essex) release.
- --
Russell Bryant
OpenStack Vulnerability Management Team
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+kdO0ACgkQFg9ft4s9SAYLsgCgptN3zZrEpOCPsbbSfPiPz7J5
han it does now.
It was applicable to all tests before nova.rpc.impl_fake was added
during Essex development.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.
opts() thing eventually anyway, as I mentioned in another message.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
On 05/04/2012 12:08 PM, Russell Bryant wrote:
> On 05/04/2012 11:53 AM, Eric Windisch wrote:
>> Russell,
>>
>> FYI, with the flags patch, it is no longer possible to set
>> rpc-implementation dependent flags in fake_flags.
>>
>> Even Rabbit has a flag in th
flag that is
> implementation/backend independent. This is uglier on the
> implementation/driver side, but cleaner on the unit tests. This is
> basically what 'fake_rabbit' is now, anyway.
As far as I can tell, this isn't actually a problem wi
On 04/30/2012 06:31 PM, Russell Bryant wrote:
> The code is in this branch:
>
> https://github.com/russellb/nova/tree/bp/versioned-rpc-apis
>
> The best place to start is in this doc:
>
> https://github.com/russellb/nova/blob/bp/versioned-rpc-apis/README-versioned-rpc-a
ersion using rpc versioning even if it could
handle it properly.
Thanks for the feedback!
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~op
e!
Thanks,
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
e feature branches could have more reviewers that are
experts in that area, but not necessarily nova-core. Hopefully these
things will help in the Folsom cycle.
Thanks to all of the core reviewers who regularly invest time into
reviewing submissions! :-)
--
Russell Bryant
__
rary application is going to be popping messages off of other
non-notification queues.
> I haven't written a ZeroMQ notifier yet, figuring that task would be
> better delayed until the move to openstack-common.
Yep, fair enough.
--
Russell Bryant
_
sure that makes sense. There would probably be a
notifier implementation specific to zeromq that could make better use of
that messaging model.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
U
that we can
maintain compatibility with the previous release.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
rently Pickles, but only because there was a
> bug in Essex at one point, breaking JSON serialization)
There may still be some datetime related problems lurking in there, but
we need to fix them as they come up. If it causes a problem for you,
it's likely a problem for the other drivers, a
hes, too.
It risks making EC2 development harder, as well. Pulling it out of nova
completely risks allowing the people that don't care about EC2 to care
even less. It could make it easier for people to make changes that make
EC2 compatibility harder to maintain.
--
Russell Bryant
--
Russell Bryant
OpenStack Vulnerability Management Team
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
On 04/17/2012 08:51 AM, Russell Bryant wrote:
> OpenStack Security Advisory: 2012-004
> CVE: 2012-2094
> Date: April 17, 2012
> Title: XSS vulnerability in Horizon log viewer
> Impact: High
> Reporter: Matthias Weckbecker
> Products: Horizon
> Affects: All versions
One c
t;
> Hey Bernhard,
>
> Are the tests using the memory transport perhaps?
Yes, it's using the memory transport.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
://review.openstack.org/#/c/6621/
References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-2094
https://bugs.launchpad.net/horizon/+bug/977944
--
Russell Bryant
OpenStack Vulnerability Management Team
___
Mailing list: https://launchpad.net/~openstack
On 04/04/2012 01:21 PM, Viktor Mauch wrote:
> Am 04.04.2012 18:29, schrieb Russell Bryant:
>> On 04/04/2012 11:36 AM, Mauch, Viktor (SCC) wrote:
>>> Hi,
>>>
>>> I just install the current source code of nova, glance and
>>> python-novaclient on a Ce
led, please check log for more info
>
> 2012-04-04 16:40:57 CRITICAL nova [-] cannot import name util
>
>
> Any idea what I do wrong?
How did you do the install? Did you use packages? If so, which ones?
--
Russell Bryant
___
Mailing l
email volume should be a factor. I think it would be
nice to have a full picture of Essex in one place.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
On 04/03/2012 12:23 PM, Jay Pipes wrote:
> On 04/03/2012 09:36 AM, Russell Bryant wrote:
>> Thanks for sharing this information. For the future, I think this type
>> of analysis and discussion is something that is great to have on the
>> mailing list instead of just a private
On 04/03/2012 10:38 AM, Mark McLoughlin wrote:
> Hey Russell,
>
> On Mon, 2012-04-02 at 16:26 -0400, Russell Bryant wrote:
>> Greetings,
>>
>> There was a thread on this list a little while ago about moving the
>> notification drivers that are in nova and glan
. I know it's more than what is needed for notifications, but
it does support what is needed for notifications (and more). I like the
idea of moving the whole thing instead of having separate messaging code
for just notifications.
--
Russell Bryant
On 04/03/2012 09:20 AM, Swamin
On 04/02/2012 08:44 PM, Xin Zhao wrote:
> On 4/2/2012 6:35 PM, Russell Bryant wrote:
>> On 04/02/2012 03:09 PM, Xin Zhao wrote:
>>> Hello,
>>>
>>> I am new to OpenStack and trying to install the diablo release on a
>>> RHEL6 cluster. I follow instruc
ummit:
http://summit.openstack.org/sessions/view/95
There are a lot of ways this could be approached. I'm going to try to
write up a proposal at some point to get a discussion moving.
--
Russell Bryant
On 04/03/2012 05:42 AM, John Garbutt wrote:
> +1 for move to nova.common
>
> I
packages that
you find in EPEL6 right now. When we update EPEL6 to Essex, which
should be within the next few weeks, horizon will be included as well.
--
Russell Bryant
___
Mailing list: https://launchpad.net/~openstack
Post to : openstac
I just threw up a patch a little while ago:
https://review.openstack.org/6119
--
Russell Bryant
On 04/02/2012 06:37 PM, Chris Behrens wrote:
> Seems like a sensible plan. Carrot can go now. I marked it deprecated so we
> can remove in folsom. I can take care of this today, even.
&
1 - 100 of 132 matches
Mail list logo
