Yes, host is from service table and hypervisor is from compute_nodes table,
I think that there are some discussion for this in Paris Summit and there
might be some change for this in Kilo.
- Detach service from compute node:
https://review.openstack.org/#/c/126895/ (implementation on a patch
Hi list,
There are two driver modes in manila currently, "multi_svm_mode" and
"single_svm_mode".
"multi_svm_mode" means usage of share-networks that contain network information
for dynamic creation of share-servers (SVMs).
"single_svm_mode" means usage of predefined some endpoint, without need
Hello all,
What is the current situation with choosing web framework? Was there any
progress in the topic? I would like to avoid forgetting about it.
2014-12-08 15:47 GMT+01:00 Ryan Petrello :
> Feel free to ask any questions you have in #pecanpy on IRC; I can answer
> a lot
> more quickly than
Hello.
There is a long living blueprint [0] about HA fencing of failed nodes
in Corosync and Pacemaker cluster. Happily, in 6.0 release we have a
pluggable architecture supported in Fuel.
I propose the following implementation [1] (WIP repo [2]) for this
feature as a plugin for puppet. It addresse
On Tue, Dec 30, 2014 at 12:56 AM, Anita Kuno wrote:
> On 12/24/2014 04:07 AM, Oleg Bondarev wrote:
> > On Mon, Dec 22, 2014 at 10:08 PM, Anita Kuno
> wrote:
> >>
> >> On 12/22/2014 01:32 PM, Joe Gordon wrote:
> >>> On Fri, Dec 19, 2014 at 9:28 AM, Kyle Mestery
> >> wrote:
> >>>
> On Fri, D
Hi Sebastian,
Nobody is forgetting this topic, especially me :) We're going to dedicate
an engineer to do some research on topic based on Ryan's comments and my
old pull request on Nailgun with Pecan. The only thing is that it's not
very high priority topic in our roadmap. Don't worry, I'm sure we
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:
But nova mounts filesystem for container by itself. Is this because rhel-6
doesn't support filesystems with type='file' or there are so
Many times when I review a revision of an existing patch, I can't see
just the change from the previous version due to other rebases. The
git-review documentation mentions this issue and suggests using -R to
make life easier for reviewers when submitting new revisions. Can some
one explain when
On Tuesday 30 December 2014 17:18:19 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:
>
>
>
>
>
>
>
> But nova mounts filesystem for container by itself. I
On 2014-12-29 23:09:20 -0800 (-0800), Adam Gandelman wrote:
[...]
> I've proposed temporary workaround to devstack-gate, which will
> hopefully allow those two to backport:
>
> https://review.openstack.org/#/c/144408/
[...]
That wasn't going to work since it ran too late. We need to catch it
betw
The default behavior, rebasing automatically, is the sane default to avoid
having developers run into unexpected merge conflicts on new patch
submissions.
But if git-review can check to see if a review already exists in gerrit
*before* doing the local rebase, I'd be in favor of it skipping the reb
On Tue, 2014-12-30 at 14:52 +0800, Lingxian Kong wrote:
> Just as what Jay Lau said, 'nova hypervisor-show '
> indeed returns host ip address, and there are more other information
> included than 'nova host-describe '. I feel a little
> confused about the 'host' and 'hypervisor', what's the differe
On 2014-12-30 09:46:35 -0500 (-0500), David Kranz wrote:
[...]
> Can some one explain when we should *not* use -R after doing 'git
> commit --amend'?
[...]
In the standard workflow this should never be necessary. The default
behavior in git-review is to attempt a rebase and then undo it
before sub
I could definitely make a Bay Area meetup.
On Mon Dec 29 2014 at 3:50:04 PM Jim Rollenhagen
wrote:
> On Mon, Dec 29, 2014 at 10:45:57PM +, Devananda van der Veen wrote:
> > I'm sending the details of the midcycle in a separate email. Before you
> > reply that you won't be able to make it, I'
On 2014-12-30 10:32:22 -0600 (-0600), Dolph Mathews wrote:
> The default behavior, rebasing automatically, is the sane default
> to avoid having developers run into unexpected merge conflicts on
> new patch submissions.
Please show me an example of this in the wild. I suspect a lot of
reviewers ar
On Dec 29, 2014, at 2:45 PM, Devananda van der Veen
mailto:[email protected]>> wrote:
That being said, I'd also like to put forth this idea: if we had a second
gathering (with the same focus on writing code) the following week (let's say,
Feb 11 - 13) in the SF Bay area -- who would atte
On Tuesday 30 December 2014 17:18:19 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:
>
>
>
>
>
>
>
> But nova mounts filesystem for container by itself. I
On Tue, Dec 30, 2014 at 8:46 AM, David Kranz wrote:
> Many times when I review a revision of an existing patch, I can't see just
> the change from the previous version due to other rebases.
I've gotten used to this. Typically when I review a new patch set I look
for my comments and make sure th
On 12/30/2014 11:37 AM, Jeremy Stanley wrote:
On 2014-12-30 09:46:35 -0500 (-0500), David Kranz wrote:
[...]
Can some one explain when we should *not* use -R after doing 'git
commit --amend'?
[...]
In the standard workflow this should never be necessary. The default
behavior in git-review is t
On 2014-12-30 12:31:35 -0500 (-0500), David Kranz wrote:
[...]
> 1. This is really a UI issue, and one that is experienced by many.
> What is desired is an option to look at different revisions of the
> patch that show only what the author actually changed, unless
> there was a conflict.
I'm not s
I'll attend. Whether it's in-person or remote is up in the air though.
Clif
On 12/30/2014 10:51 AM, Jay Faulkner wrote:
>
>> On Dec 29, 2014, at 2:45 PM, Devananda van der Veen
>> mailto:[email protected]>> wrote:
>>
>> That being said, I'd also like to put forth this idea: if we had a
>>
There will be a new working group meeting for improving the consumability
of infra CI components and documentation. The vote has been tallied and the
meeting times will be Wednesdays at 1500/0400 UTC alternating. The existing
meeting at 1800 UTC on Monday January 5th (and all future meetings at tha
Thanks for your votes. Changes have been applied. Welcome Motohiro/Yuanying
Otsuka to the core group.
Regards,
Adrian
On Dec 26, 2014, at 12:44 PM, Adrian Otto wrote:
> Magnum Cores,
>
> I propose the following addition to the Magnum Core group[1]:
>
> + Motohiro/Yuanying Otsuka (ootsuka)
>
Hi,
I have a VM with an interface attached to network “provider-net-1” and assigned
IP 66.0.0.8.
localadmin@qa4:~/devstack$ nova list
+--+--+++-+--+
| ID | Name |
+1
2014-12-27 19:02 GMT+01:00 Devdatta Kulkarni <
[email protected]>:
> +1
>
> --
> *From:* James Y. Li [[email protected]]
> *Sent:* Saturday, December 27, 2014 9:03 AM
> *To:* OpenStack Development Mailing List
> *Subject:* Re: [openstack-dev] [Solum]
Thanks Kevin for your clarification, which further affirms my belief
that ip address should be included in the host info.
I will contact Jay Pipes on IRC, to see what can I help towards this
effort, soon after the New Year's Day in China. :)
2014-12-31 0:34 GMT+08:00 Kevin L. Mitchell :
> On Tue,
26 matches
Mail list logo
