Re: [openstack-dev] OpenStack upstream specs - Invitation to edit

Hey James, I'am unable to open this document :( TP (Tomasz from Intel) On Tue, Oct 18, 2016 at 2:35 PM, James Penick (via Google Docs) < jpen...@gmail.com> wrote: > James Penick has invited you to *edit* the following > document: > OpenStack upstream specs >

Re: [openstack-dev] [ironic][nova] Suggestion required on pci_device inventory addition to ironic and its subsequent changes in nova

On Apr 10, 2017 1:02 PM, "John Garbutt" wrote: On 10 April 2017 at 11:31, . With ironic I thought everything is "passed through" by default, because there is no virtualization in the way. (I am possibly incorrectly assuming no BIOS tricks to turn off or re-assign PCI devices dynamically.) It'

Re: [openstack-dev] [all][ironic] Kubernetes-based long running processes

On 16 Mar 2017 6:21 pm, "Dean Troyer" wrote: Before implementing something new it would be a good exercise to have a look at the other existing ways to run VMs and containers already in the OpenStack ecosystem. Service VMs are a thing, and projects like Octavia are built around running inside

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Etcd seems to be a better choice for performance reasons as well: https://coreos.com/blog/performance-of-etcd.html TP On 14 Mar 2017 12:45 am, "Davanum Srinivas" wrote: > On Tue, Mar 14 2017, Davanum Srinivas wrote: > > > Let's do it!! (etcd v2-v3 in tooz) > > Hehe. I'll move that higher in my

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

Hey Steven, answers inline. On Mon, Apr 25, 2016 at 9:27 AM, Steven Dake (stdake) wrote: > > I disagree with your assertion. You are gaming your data to provide the > worst possible container (nova) because the RPMs pull in libvirt. Kolla > has no control over how Red Hat choses to package RDO

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

On Mon, Apr 25, 2016 at 5:51 AM, Jeffrey Zhang wrote: > > I do not think this is the issue of Kolla. It is a issue of Docker > images. All the docker images has such issue. This should be solved > in the docker side. > It's a kolla issue and they way project build images. Calling yum install in D

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

On Mon, Apr 25, 2016 at 7:11 AM, Michał Rostecki wrote: > > Ummm... no? > > If you want to upgrade the things in containers, you should just > rebuild them. You don't do any "yum update" action by hand in some > middle layer. The newest updated repo metadata come from the base > image and your lay

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

On Sat, Apr 23, 2016 at 2:27 AM, Steven Dake (stdake) wrote: > > Trying to understand the issue here, do you believe the current jinja2 > Dockerfiles are not readable? I'm pretty sure my 11 and 13 year old > children which are just learning programming already understand conditionals > and variab