Hi.
I'm using Openstack Ocata and trying Magnum.
I encountered a lot of problems but I been able to solved many of them.
Now I'm curious about your experience with Magnum. ¿Any success stories?
¿What about more recent versions of k8s (1.7 or 1.8)? ¿What driver is, in
your opinion, better: Atomic
We have 6 keystone servers on 2 datacenters on 6 different servers behind 2
Load Balancers.
One server rotates the tokens and then send the files to the rest of the
servers via rsync --delete.
Cheers.
P.D: We use kolla with docker so this works even with docker volumes.
El mar., 7 feb. 2017 a l
adow tenant can certainly do
> with some improvement, seems like a good thing to do once the code gets
> fixed up.
>
> -amrith
>
> ---
>
> From: Sergio Morales Acuña [mailto:sem...@gmail.com]
> Sent: Tuesday, February 7, 2017 1:43 AM
> To: Sam Morrison
> Cc: opensta
orth asking in the
> openstack-trove IRC channel or on the openstack-dev mailing list (adding a
> [trove] in the subject should get their attention) to get some answers to
> this question.
>
> Cheers,
> Sam
>
>
> > On 4 Feb 2017, at 1:34 am, Sergio Morales Acuña
Hi.
I'm looking for information about the "Trove Shadow Tenant" feature.
There some blogs talking about this but I can't find any information about
the configuration.
I have a working implementation of Trove but the instance is created in the
same project as the user requesting the database. Thi
know about even without an update.
>
> @Sergio,
>
> Can you open a bug for this and provide exact steps to reproduce this?
>
>
> Thanks,
> Kevin Benton
>
> On Wed, Oct 5, 2016 at 12:50 AM, Ihar Hrachyshka
> wrote:
>
> Sergio Morales Acuña wrote:
>
>
Thanks for the heads up.
El mié., 5 oct. 2016 a las 4:50, Ihar Hrachyshka ()
escribió:
> Sergio Morales Acuña wrote:
>
> > Hi.
> >
> > I'm facing a problem related to dns_name and dnsmasq.
> >
> > Nova and Neutron can create a port with dns_nam
Hi.
I'm facing a problem related to dns_name and dnsmasq.
Nova and Neutron can create a port with dns_name and dnsmasq it's correctly
updating "/addn_host".
The problem is when Nova boot an instance using a new or previusly created
port. The port has the correct dns_name but dnsmaq (dhcp_agent)
Hi all.
I'm looking for documentation or articles about cross-region communication
at tenant level (if possible).
Can someone share links about this and similar topics?
Thank you.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack
Hi.
After running a neutron-ovs-cleanup and restarting openvswitch-agent and
nova-compute with all the VMs running, nova does not add existing ports
to br-int.
All qvb@qvo exists but, after restarting nova-compute, only qvo from new
machines are added correctly to the br-int.
If I reboot the
10 matches
Mail list logo
