On Mon, Jun 25, 2012 at 6:03 PM, Tommi Virtanen wrote:
> On Sat, Jun 23, 2012 at 11:42 AM, Igor Laskovy wrote:
>> Hi all from hot Kiev))
>>
>> Does anybody use Ceph as a backend storage for NOVA-INST-DIR/instances/ ?
Yes. http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/
Just wanted to say thanks to Vish, Sébastien and Adam for their input
on this thread. I haven't been able to return to my test setup to try
out the suggestions, but hope to be able to do so in the next few
days.
Lest you think I'm ignoring you. :)
Cheers,
Florian
On Fri, Jun 22, 2012 at 7:43 AM, James Page wrote:
You can type faster than I can... I'm working on getting this
resolved in the current dev release of Ubuntu in the next few
days after which it will go through the normal SRU process for
Ubuntu 12.04.
>> Sweet, thanks!
>
> The
Hi everyone,
perhaps someone can shed some light on a floating IP issue.
I have 2 nova-compute nodes (call them alice and bob), one of them
(alice) is also running nova-network. bob uses alice as its
--metadata_host and --network_host.
I assign a floating IP to a guest running on bob. Expectedly
On 06/10/12 23:32, Sébastien Han wrote:
> Hello everyone,
>
> I recently posted on my website an introduction to ceph and the
> integration of Ceph in OpenStack.
> It could be really helpful since the OpenStack documentation has not
> dealt with it so far.
>
> Feel free to comment, express your o
On Fri, Jun 8, 2012 at 5:59 PM, James Page wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Josh
>
> On 08/06/12 16:48, Josh Durgin wrote:
>> There's an Ubuntu bug already:
>>
>> https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/981130
>>
>> librgw was not complete, and wasn't a
On Fri, Jun 8, 2012 at 5:48 PM, Josh Durgin wrote:
> Hi Florian,
>
> There's an Ubuntu bug already:
>
> https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/981130
>
> librgw was not complete, and wasn't actually used by radosgw, so it was
> dropped. The Ubuntu package just needs to be updated to r
Hi everyone,
apologies for the cross-post, and not sure if this is new information.
I did do a cursory check of both list archives and didn't find
anything pertinent, so here goes. Feel free to point me to an existing
thread if I'm merely regurgitating something that's already known.
Either I'm d
On Thu, Jun 7, 2012 at 9:53 AM, Thierry Carrez wrote:
> Florian Haas wrote:
>> a few people have reported issues with live migration lately, and
>> I've been digging into them to narrow them down.
>>
>> The symptom is relatively easy to describe: you run "n
Hi everyone,
a few people have reported issues with live migration lately, and
I've been digging into them to narrow them down.
The symptom is relatively easy to describe: you run "nova live-migration
", and nothing happens.
A few words of background:
- System is Ubuntu precise with stock pack
On 06/05/12 17:27, Vishvananda Ishaya wrote:
> No, migrate does "dead" migration on a server. Essentially snapshots the
> drive transfers it to a new server and reboots. Migrate and live-migration
> do need to be consolidated.
Um, OK. How do I specify where to migrate to?
nova help migrate
us
On 06/05/12 14:45, Anne Gentle wrote:
> In a word, yes.
>
> I noticed this yesterday but hadn't logged a bug about it, thanks Florian.
https://review.openstack.org/8181
https://review.openstack.org/8182
Cheers,
Florian
___
Mailing list: https://launch
Hi everyone,
do I understand correctly that "nova migrate" is intended to upgrade
an instance's configuration from one Nova version to the next? I can't
seem to find it documented anywhere, and would be happy to provide a
doc patch if my hunch is correct.
Also if my assumption is correct, would p
Hi everyone,
apologies that this took me longer than expected; I had to fight a few
fights with Maven, and resort to Anne's direct help, to get to this
point (thanks again Anne).
I've just submitted a documentation change to Gerrit that's a result
of the high-availability session we had at the Fo
Stephen,
On Fri, May 25, 2012 at 3:18 PM, Stephen Gran
wrote:
> Hello,
>
> I am investigating various high availability options for a pending
> deploy of open stack. One of the obvious services to make resilient is
> the mq service. We're going to be using rabbitmq, and we'll most likely
> have
Hi everyone,
apologies for the cross-post; I believe this might be interesting to
people on both the openstack and the pacemaker lists. Please see
below.
On Tue, Feb 14, 2012 at 9:07 AM, i3D.net - Tristan van Bokkem
wrote:
> Hi Stackers,
>
> It seems running Openstack components in High Availabi
For some reason it appears that Darren's message is late in making it
into my inbox, so I'm replying to Tristan's response instead.
On Tue, Feb 21, 2012 at 3:40 PM, i3D.net - Tristan van Bokkem
wrote:
> Agreed, but you're talking about HA at a different layer - within the
> applications that will
On Tue, Feb 21, 2012 at 12:51 PM, Darren Birkett
wrote:
> Surely it depends what you want out of it? If just pure high
> availability (ie ability to continue functioning when primary node
> goes down), then doesn't a master/master with floating IP fit the
> bill?
Master/master with a floating I
On Tue, Feb 21, 2012 at 12:34 PM, i3D.net - Tristan van Bokkem
wrote:
> Ho Florian,
>
> I respect your opinion of course and I am not here to start a fight. Point
> is, how I understand it Nova really isn't very flexible on High Availability
> terms. I have now a master/master mysql setup with a V
On Thu, Feb 16, 2012 at 3:09 PM, Tom Ellis wrote:
> nova-volume service
> * Current weakness in the HA setup, unless you are willing to use iscsi
> tgtd with DRBD. I believe this would still have some problems when
> failing over with the initiators that are logged in.
Nope, this is well underst
20 matches
Mail list logo
