Re: [Openstack] [Fuel] How to configure Xen + Libvirt using Fuel 8.0

2016-04-03 Thread Ashish Yadav
Hi Bob, On Fri, Apr 1, 2016 at 10:13 PM, Bob Ball wrote: > XenServer is fully open source - XCP is no longer. You can download > XenServer for free from www.XenServer.org without any contact with Citrix. > > For libvirt+Xen AFAIK that plugin doesn't exist and you would need

Re: [openstack-dev] [horizon][all] How to properly depend on Horizon

2016-04-03 Thread Akihiro Motoki
Hi Serg, I proposed another way to sahara-dashboard [1]. This is the way used in neutron sub-projects. It also allows us to use constrained environments used in OpenStack gate jobs. I believe it works for all horizon related projects. I agree the simplest way is to publish horizon to PyPI, but

[Openstack-operators] Draft Agenda for AUS Ops@Summit

2016-04-03 Thread Tom Fifield
Hi all, I've taken the suggestions from the etherpad and attempted to wrangle them into something that would fit in the space we have with as few conflicts as possible. As a reminder, we have two different kind of sessions - General Sessions, which are discussions for the operator

Re: [OpenStack-Infra] multiple gerrit connections for ZUUL

2016-04-03 Thread Joshua Hesketh
Hello Vaclav, Thanks for raising this, it looks like you've found a bug. The layout validation test doesn't load the scheduler fully meaning that the scheduler is unaware of the connections and hence you see errors like the ones you've exampled. If you start the zuul server without -t you

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

2016-04-03 Thread Andrew Beekhof
On Tue, Mar 29, 2016 at 6:02 AM, Dan Prince wrote: [...] > That said regardless of what we eventually do with Pacemaker or Puppet > it should be feasible for them both to co-exist. The key thing to keep in mind if you're using Puppet to build a cluster is that if you're

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

2016-04-03 Thread Steven Dake (stdake)
On 4/3/16, 6:38 PM, "Dan Prince" wrote: > > > >On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote: >> As of the Liberty release, Magnum now supports provisioning Mesos >> clusters, so TripleO wouldn't have to maintain the installer for >> that >> either. (The choice of

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

2016-04-03 Thread Steven Dake (stdake)
From: Dan Prince > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Sunday, April 3, 2016 at 4:54 PM To: "OpenStack Development Mailing List

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

2016-04-03 Thread Dan Prince
On Wed, 2016-03-23 at 19:11 +, Fox, Kevin M wrote: > If heat convergence worked (Is that a thing yet?), it could > potentially be used instead of a COE like kubernetes. > > The thing ansible buys us today would be upgradeability. Ansible is > config management, but its also a workflow like

[openstack-dev] [horizon][all] How to properly depend on Horizon

2016-04-03 Thread Serg Melikyan
Hi folks, while I was working on bug [0] with incorrect dependency to horizon in stable/mitaka I discovered at least three different ways how people add such dependency: 1. tarball dependency in tox.ini [1] 2. tarball dependency in test-requirements.txt [2] 3. git repo dependency in

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

2016-04-03 Thread Dan Prince
On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote: > As of the Liberty release, Magnum now supports provisioning Mesos  > clusters, so TripleO wouldn't have to maintain the installer for > that  > either. (The choice of Mesos is somewhat unfortunate in our case,  > because Magnum's

Re: [openstack-dev] [TripleO] tripleo-quickstart import

2016-04-03 Thread Steve Baker
On 30/03/16 13:37, John Trowbridge wrote: On 03/29/2016 08:30 PM, John Trowbridge wrote: Hola, With the approval of the tripleo-quickstart spec[1], it is time to actually start doing the work. The first work item is moving it to the openstack git. The spec talks about moving it as is, and

[openstack-dev] [horizon][mitaka][all] Update dependency to horizon for stable/mitaka

2016-04-03 Thread Serg Melikyan
Hi folks, I've noticed that several projects which have dashboard which depend on horizon reference incorrect version [0]: * designate-dashboard * mistral-dashboard * murano-dashboard (fix proposed) * manila-ui * ironic-ui * searchlight-ui * magnum-ui * monasca-ui all these projects, and some

Re: [openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

2016-04-03 Thread Jamie Lennox
On 2 April 2016 at 09:21, Rodrigo Duarte wrote: > > > On Thu, Mar 31, 2016 at 1:11 PM, Matthew Treinish > wrote: > >> On Thu, Mar 31, 2016 at 11:38:55AM -0400, Minying Lu wrote: >> > Hi all, >> > >> > I'm working on resource federation at the

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

2016-04-03 Thread Dan Prince
On Thu, 2016-03-31 at 08:22 +, Steven Dake (stdake) wrote: > Kevin, > > I am not directly answering your question, but from the perspective > of Kolla, our upgrades are super simple because we don't make a big > mess in the first place to upgrade from.  In my experience, this is > the number

Re: [Openstack] Problem Trouble Shooting while integrating/installing Trove with OpenStack. [ssl certificate error] [cant find the matching version of pip<8]

2016-04-03 Thread Amrith Kumar
Mohan, To help you further, we definitely need to get a better understanding of what you may have been doing at the time. So here are some questions. 1. What is your setup 2. What version of OpenStack and Trove are you using 3. What did you do when you got this error 4. Could you share

Re: [openstack-dev] [murano][release] missing build artifacts

2016-04-03 Thread Serg Melikyan
Hi Doug, I +1 your commit with removing build artifacts for openstack/murano-apps repo, we indeed don't have artifacts for murano-apps. >It would be good to understand what your intent is for builds. Can you follow >up here on this thread with some details? openstack/murano-apps contains set

Re: [Openstack-operators] [nova] Removing seeded flavors

2016-04-03 Thread Robert Starmer
I'll add a vote for removal, given how varied private clouds tend to be, the flavors are often "wrong" for any one particular purpose. R On Sat, Apr 2, 2016 at 8:41 PM, Mike Smith wrote: > +1 from me. We always just remove them and add our own. Like Dan said, > it’s

[openstack-dev] [OpenStack-Ansible] Mitaka release

2016-04-03 Thread Jesse Pretorius
The OpenStack-Ansible project is pleased to announce the availability of it's Mitaka release, v13.0.0, and with it comes the following features: Increased modularity: The Ansible roles we provide deploy OpenStack services directly from a git source into python venvs, and deploy their key

[openstack-dev] [fuel]

2016-04-03 Thread Kyrylo Galanov
Hi team, An issue with rsync was recently reported [0]. We have a symlink 'liberty-9.0/modules/osnailyfacter/modular/master' to examples directory in a fuel master node. However, rsync does not copy the symlink to slave nodes. Being easy to fix (by adding -l flag) this issue raises a question: do

[Openstack] Problem Trouble Shooting while integrating/installing Trove with OpenStack. [ssl certificate error] [cant find the matching version of pip<8]

2016-04-03 Thread Mohan N V
I have setup openstack in my laptop. I need to store some database in cloud, so i tried to integrate trove (database as a service) with openstack. but trouble shooting with the above errors. I want to install openstack in another laptop. But still iI'm getting the same errors as mentioned above.

[Openstack] [OpenStack] [Fuel] [Networks] Verification failed

2016-04-03 Thread Alexandr Porunov
Hello, I have created two networks in VirtualBox: vboxnet0 : 192.168.56.0 /24 vboxnet1 : 192.168.57.0 /24 vboxnet0 is a public network (gateway on 192.168.56.10) vboxnet1 is a private network Each virtual machine is connected to the private and public networks (Fuel Master and two Fuel Slaves