Hi Team,
I know there is a polling on the new IRC meeting time, but before we gather
more inputs, let's keep using the old time slot for this week (10PM Beijing
Time/9AM EST/6AM PST)
Agenda for this week's meeting:
1. Status update on NOVA interaction spec
2. Status update on DB scheme spec
3.
The pod concept allows you to have one tool per container do one thing and do
it well.
You can have a container for generating config, and another container for
consuming it.
In a Kubernetes pod, if you still wanted to do puppet,
you could have a pod that:
1. had an init container that ran
Hi,
I'm trying to setup pacemaker for live-migration when a compute node
hosting the VM goes down.
So, I created cluster resource for the compute-instance (demo1) with
'VirtualDomain' resource agent.
>>> pcs resource create demo1 VirtualDomain
migrateuri="qemu+tcp://:16509/system"
REMINDER: The openstack, openstack-dev, openstack-sigs and
openstack-operators mailing lists (to which this was sent) are being
replaced by a new openstack-disc...@lists.openstack.org mailing
list. The new list[0] has been open for posts from subscribers since
Monday November 19, and the old lists
On Tue, 2018-11-27 at 16:24 +0100, Bogdan Dobrelya wrote:
> Changing the topic to follow the subject.
>
> [tl;dr] it's time to rearchitect container images to stop incluiding
> config-time only (puppet et al) bits, which are not needed runtime
> and
> pose security issues, like CVEs, to
Hi folks,
as just mentioned in the tripleo weekly irc meeting [1] some of us are
trying to make small weekly improvements to the tripleo docs [2]. We are
using this bug [3] for tracking and this effort is a result of some
feedback during the recent Berlin summit.
The general idea is 1 per week
Changing the topic to follow the subject.
[tl;dr] it's time to rearchitect container images to stop incluiding
config-time only (puppet et al) bits, which are not needed runtime and
pose security issues, like CVEs, to maintain daily.
Background:
1) For the Distributed Compute Node edge case,
