On 1 October 2013 19:31, Clint Byrum wrote:
> TripleO meets at 2000 UTC every Tuesday.
1900UTC.
:)
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.op
>> 1) Please *do not* Approve or Reverify stable/* patches. The pyparsing
>> requirements conflict with neutron client from earlier in the week is still
>> not resolved on stable/*.
>
> Also there's an issue with quantumclient and Nova stable/grizzly:
> https://jenkins01.openstack.org/job/periodic-
Thank you for your answer Clint.
I try to debug .and, I set up TripleO by real hadware to use.
2013/10/1 Clint Byrum
> Excerpts from hideyasu hayashi's message of 2013-09-30 18:29:24 -0700:
> > Dear List,
> >
> >
> >
> > Hi, I set up TripleO devtest environment on VMware(Ubuntu 12.04.3 LTS)
Hi Mike and Zane,
Le 27/09/2013 15:58, Mike Spreitzer a écrit :
Zane Bitter wrote on 09/27/2013 08:24:49 AM:
> Your diagrams clearly show scheduling happening in a separate stage to
> (infrastructure) orchestration, which is to say that at the point where
> resources are scheduled, their actua
All,
So I wrote out an article the other day on the background to the keystoneclient
changes that I've been trying to get through.
Please take a look:
http://www.jamielennox.net/blog/2013/09/27/apiclient-communications/
I'm hoping that it gives a better understanding of the concepts and the
Hi Gary,
2013/9/29 Gary Kotton :
> Not related to the stable branches, but related to trunk. At the moment I am
> working on https://review.openstack.org/#/c/47788/. This patch adds a
> timeout to the access to the OVS database.
There are ovs-vsctl calls on stable/grizzly too, shouldn't this be b
Clint Byrum wrote on 01.10.2013 08:31:44 - Excerpt:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 01.10.2013 08:33
> Subject: Re: [openstack-dev] [heat] [scheduler] Bringing things
> together for Icehouse (now featuring software orchestration)
>
> Excerpts from Georgy Okrokvertskhov's messag
All, you can view the bug here:
https://bugs.launchpad.net/glance/+bug/1222369
Thanks,
Maty.
-Original Message-
From: Iccha Sethi [mailto:iccha.se...@rackspace.com]
Sent: Monday, September 30, 2013 17:51
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Waiting for so
Alan Pevec wrote:
>>> 1) Please *do not* Approve or Reverify stable/* patches. The pyparsing
>>> requirements conflict with neutron client from earlier in the week is still
>>> not resolved on stable/*.
>>
>> Also there's an issue with quantumclient and Nova stable/grizzly:
>> https://jenkins01.ope
Warning, this is a little long, but it's the distillation of a
2.mumble hour call I had late last week with Devananda and Clint. It's
a proposal: please do comment and critique it.
The tl;dr read is:
- we've been doing good work
- but most of us are currently focused on the tech rather than the
On Mon, Sep 30, 2013 at 02:25:30PM -0700, Ravi Chunduru wrote:
> Alessandro,
> I agree with you. I created a Blueprint. Let us collaborate and achieve
> this on all types of hypervisors.
>
> All,
>
> Here is the link for the BP as discussed.
> https://blueprints.launchpad.net/nova/+spec/applianc
+1
On Mon, Sep 23, 2013 at 7:38 PM, Emilien Macchi wrote:
> +1
>
> Anne is doing without any doubt an amazing job on OpenStack manuals.
>
> Thank you Anne,
>
> Emilien Macchi
>
> # OpenStack Engineer
> // eNovance Inc. http://
Today in the project/release status meeting, we expect a busy meeting as
we examine the last blockers before RC1. That includes looking into the
gate flaky tests that have been pleguing our velocity lately. In order
to issue the RC1s in the near future, we may have to restrict gating to
RC1-critica
On 1 October 2013 21:37, Robert Collins wrote:
> - https://trello.com/tripleo as an experimental kanban for this [1]
This was private; sorry - fixed!
Also, I forgot to include a link to
https://wiki.openstack.org/wiki/TripleO/TripleOCloud which is draft
documentation about this proposed cloud.
Hi,
Anne Gentle has been working consistently with me and my team from the time
we released the OpenStack Beginner's
Guide Diablo and Essex releases. Her work with Openstack manual project is
well known through out the community.
I am supporting Anne Gentle's candidature for OpenStack documentati
Yes, it should. I'll mark the bug as a stable backport
Thanks
On 10/1/13 10:51 AM, "Alan Pevec" wrote:
>Hi Gary,
>
>2013/9/29 Gary Kotton :
>> Not related to the stable branches, but related to trunk. At the moment
>>I am
>> working on https://review.openstack.org/#/c/47788/. This patch adds a
>
Hi,
I have just found out that there's already a source package called
"trove" in Debian:
http://packages.debian.org/source/sid/trove
Lucky, I don't think it will clash with OpenStack trove since it
produces libtrove-java* .deb files, though that's quite annoying. The
source package for OpenStac
Maybe the answer is hiding in plain sight: host aggregates. This is a
concept we already have, and it allows identification of arbitrary
groupings for arbitrary purposes.___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.open
Clint Byrum wrote on 10/01/2013 02:38:53 AM:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 10/01/2013 02:40 AM
> Subject: Re: [openstack-dev] [scheduler] [heat] Policy specifics
> (for holistic infrastructure scheduling)
>
> Mike, this has been really fun, but it is starting to feel like
On Tue, Oct 1, 2013 at 1:17 AM, Henry Nash wrote:
> I think an obvious first step of domain support outside keystone is for
> images. Today, I believe, an image can be global or project based. There
> is definitely a use case for a third state of being domain based - and
> hence available to all
Hi,
Don is on vacation. Lets try and have the meeting today.
Topics that come to mind:
1. Consolidating ideas regarding scheduling API's that we can propose for
summit – it would be great if we could come with a crystalized proposal for the
community
2. On the mail list there has been a lot
On Oct 1, 2013, at 6:45 AM, Thomas Goirand wrote:
> Hi,
>
> I have just found out that there's already a source package called
> "trove" in Debian:
>
> http://packages.debian.org/source/sid/trove
>
> Lucky, I don't think it will clash with OpenStack trove since it
> produces libtrove-java* .de
Good idea, I'm very interested in that!
2013/10/1 Vishvananda Ishaya
>
> On Sep 30, 2013, at 1:12 AM, Daniel P. Berrange
> wrote:
>
> > On Fri, Sep 27, 2013 at 02:11:36PM -0400, Solly Ross wrote:
> >> Hello Fellow OpenStackers,
> >>
> >> I was working on a bug (
> https://bugzilla.redhat.com/s
On 10/1/2013 10:53 AM, Michael Basnight wrote:
Well this sucks. Im not sure im a fan of renaming it because of the previous
existence of a package. Renaming is not fun. Ill let the more experienced
openstack peoples help decide on this...
Certainly it's not fun, but wouldn't it be easier t
On Oct 1, 2013, at 8:00 AM, Nicholas Chase wrote:
>
>
> On 10/1/2013 10:53 AM, Michael Basnight wrote:
>
>> Well this sucks. Im not sure im a fan of renaming it because of the previous
>> existence of a package. Renaming is not fun. Ill let the more experienced
>> openstack peoples help deci
Hello,
I am wondering if we should handle potential issues (unlikely to happen
with the current code) now or wait to see what happens with the code in the
future ?
What I am referring to can be seen for example
in neutron/db/db_base_plugin_v2.py in _recycle_ip if we try to recycle the
same IP twic
On 10/01/2013 10:02 PM, Jonathan Dowland wrote:
> On Tue, Oct 01, 2013 at 09:45:17PM +0800, Thomas Goirand wrote:
>> Since I have already uploaded python-troveclient (currently waiting in
>> the FTP master's NEW queue), OpenStack troveclient will be in Sid, but
>> if some day, someone wants to uplo
Hi fellow Trove devs,
With the Designate project ramping up, its time to refactor the ancient DNS
code that's in Trove to work with Designate.
The good news is since the beginning, it has been possible to add new drivers
for DNS in order to use different services. Right now we only have a drive
On 10/01/2013 11:45 AM, Thomas Goirand wrote:
> On 10/01/2013 10:02 PM, Jonathan Dowland wrote:
>> On Tue, Oct 01, 2013 at 09:45:17PM +0800, Thomas Goirand wrote:
>>> Since I have already uploaded python-troveclient (currently waiting in
>>> the FTP master's NEW queue), OpenStack troveclient will
We have vagrant working with virtual box to start up a trove development
environment. This was tested with VirtualBox on an Ubuntu machine but
should work with any other environment as well. This is nice and should
benefit the community to setup trove easily in multiple environments.
This repo may
On 10/01/2013 12:02 AM, Alan Pevec wrote:
>>> 1) Please *do not* Approve or Reverify stable/* patches. The pyparsing
>>> requirements conflict with neutron client from earlier in the week is still
>>> not resolved on stable/*.
>> Also there's an issue with quantumclient and Nova stable/grizzly:
>>
On 10/01/2013 11:23 PM, Michael Basnight wrote:
>
> On Oct 1, 2013, at 8:00 AM, Nicholas Chase wrote:
>
>>
>>
>> On 10/1/2013 10:53 AM, Michael Basnight wrote:
>>
>>> Well this sucks. Im not sure im a fan of renaming it because of the
>>> previous existence of a package. Renaming is not fun. Ill
Hey all!
The job to automatically propose syncs from the openstack/requirements
repo went live today - as I'm sure you all noticed, since pretty much
everyone got a patch of at least some size.
The job works the same way as the translations job - it will propose a
patch any time the global repo c
Hi,
First of all, before I reply, I'd like to tell that hopefully, I believe
we're fine in this specific case (at least on the Debian side of
things). Though it really shouldn't have happen, and I believe it's my
role to warn everybody about the risks.
On 10/02/2013 12:02 AM, Monty Taylor wrote:
Thx for getting this squared away zigo!!
On Oct 1, 2013, at 10:40 AM, Thomas Goirand wrote:
> Hi,
>
> First of all, before I reply, I'd like to tell that hopefully, I believe
> we're fine in this specific case (at least on the Debian side of
> things). Though it really shouldn't have happen, and
Hi All,
Over the last few weeks, I've been working on compiling a list of metrics and
representing these metrics via wireframes that are important to show to users
on the Node, Rack(Logical Group), and Resource Class details pages in Tuskar.
These have been designed keeping the metrics that Cei
Hi Neutron VPNaaS folks
In havana, IPsec site-to-site model and reference driver is merged.
Let's discuss next step! :P
I have created a page for this discussion.
so could you add your bp or thought or workitem on this etherpad page.
https://etherpad.openstack.org/NeutronVPNaaSIceHouse
I have a
On 10/01/2013 01:40 PM, Thomas Goirand wrote:
> Hi,
>
> First of all, before I reply, I'd like to tell that hopefully, I believe
> we're fine in this specific case (at least on the Debian side of
> things). Though it really shouldn't have happen, and I believe it's my
> role to warn everybody ab
On Mon, Sep 30, 2013 at 4:23 PM, Elizabeth Krumbach Joseph
wrote:
> The OpenStack Infrastructure (Infra) team is hosting our weekly
> meeting tomorrow, Tuesday October 1st, at 19:00 UTC in
> #openstack-meeting
Minutes:
http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-10-01-19.01.htm
Infra have a move slot this weekend and *tuskar* are now queued up to
move at that point.
Once we've moved them, they will have their test runs coerced to use
the official mirror and requirements sets; we may find that breaks
current tests that are using the looser rules from stackforge - if so,
i
Folks:
Just an update regarding the change to move devstack to default
to the ML2 Neutron plugin instead of the OVS plugin. The patch [1]
merged yesterday. Full tempest tests were passed with this, but
just a heads up for those using devstack without specifying a
Neutron plugin specifically.
Than
Congrat!
2013/10/1 Kyle Mestery (kmestery) :
> Folks:
>
> Just an update regarding the change to move devstack to default
> to the ML2 Neutron plugin instead of the OVS plugin. The patch [1]
> merged yesterday. Full tempest tests were passed with this, but
> just a heads up for those using devstac
On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson wrote:
> Hi fellow Trove devs,
>
> With the Designate project ramping up, its time to refactor the ancient
> DNS code that's in Trove to work with Designate.
>
> The good news is since the beginning, it has been possible to add new
> drivers for DNS in
> On Oct 1, 2013, at 3:06 PM, Ilya Sviridov wrote:
>
>
>> On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson
>> wrote:
>> Hi fellow Trove devs,
>>
>> With the Designate project ramping up, its time to refactor the ancient DNS
>> code that's in Trove to work with Designate.
>>
>> The good news is s
Ilya you make a good point. We shouldn't spend time massively change the DNS
code if we'll just have to do it again so that HEAT can do everything for us.
I echo Mike's comments though that if for some reason someone wants Designate
support before we get HEAT integrated they should be able to ad
Hi all,
I read a similar topic was discussed before but it seems like no specific
and clear solution is provided in that discussion, anyone has the same
issue before and already solved it?
According to the vmware vsphere networking instruction, I create a port
group with the same name as the 'vm
We'd like to get tuskar projects doing releases sooner rather than
later. For python-tuskarclient, this is pretty much a no-brainer : we
just need to start doing it.
However, for tuskar-ui and tuskar it's more complex.
# tuskar
This is an API service; whats the story for non-integrated projects
Kyle, what is the proper way to configure ML2 plugin (I plan to use OVS
with VLAN) in localrc?
Thanks,
Richard
On Tue, Oct 1, 2013 at 5:12 PM, Kyle Mestery (kmestery)
wrote:
> Folks:
>
> Just an update regarding the change to move devstack to default
> to the ML2 Neutron plugin instead of the O
great job! thanks
(how about auto sync from oslo too?
- projects.txt: projects want to be automatically synced from oslo
- heads.txt: HEAD for each module in oslo
whenever module maintainer think current module is strong enough to
publish, then he/she can edit the heads.txt of that module line, t
> On Oct 1, 2013, at 3:37 PM, Michael Basnight wrote:
>
>> On Oct 1, 2013, at 3:06 PM, Ilya Sviridov wrote:
>>
>>
>>> On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson
>>> wrote:
>>> Hi fellow Trove devs,
>>>
>>> With the Designate project ramping up, its time to refactor the ancient DNS
>>> c
Richard,
Please look at https://wiki.openstack.org/wiki/Neutron/ML2
If anything is unclear or doesn't work please follow up so we can tweak the
wiki.
-- Henry
On Tue, Oct 01, at 9:33 pm Richard Woo (richardwoo2...@gmail.com) wrote:
> Kyle, what is the proper way to configure ML2 plugin (I plan
> On Sep 26, 2013, at 8:49 AM, Michael Basnight wrote:
>
>> On Sep 25, 2013, at 7:16 PM, Craig Vyvial wrote:
>>
>> So we have a blueprint for this and there are a couple things to point out
>> that have changed since the inception of this BP.
>>
>> https://blueprints.launchpad.net/trove/+spe
This patch is a fix for a bug that's blocking all stable branch patches
from getting through Jenkins:
https://review.openstack.org/#/c/49006/
Jenkins is failing on it because it runs devstack from master which uses
python-neutronclient but this is a fix for the quantumclient branch (which
stab
On Oct 1, 2013, at 7:06 PM, Vipul Sabhaya wrote:
> On Oct 1, 2013, at 3:37 PM, Michael Basnight wrote:
>
>> On Oct 1, 2013, at 3:06 PM, Ilya Sviridov wrote:
>>
>>>
>>> On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson
>>> wrote:
>>> Hi fellow Trove devs,
>>>
>>> With the Designate project rampin
On Oct 1, 2013, at 7:19 PM, Vipul Sabhaya wrote:
>
> So from this API, I see that a configuration is a standalone resource that
> could be applied to N number of instances. It's not clear to me what the API
> is for 'applying' a configuration to an existing instance.
https://wiki.openstack.o
On 10/01/2013 08:08 PM, Robert Collins wrote:
> We'd like to get tuskar projects doing releases sooner rather than
> later. For python-tuskarclient, this is pretty much a no-brainer : we
> just need to start doing it.
Yup. Just do it.
> However, for tuskar-ui and tuskar it's more complex.
>
>
On 2 October 2013 18:20, Monty Taylor wrote:
>> # tuskar-ui
>>
>> This is a Horizon plugin -
>> http://git.openstack.org/cgit/stackforge/tuskar-ui/tree/docs/install.rst#n57
>> - so it's not super clear to me how to make releases of it. Should it
>> really just be in the Horizon tree?
>
> Oy. No c
In Savanna we're supplying "plugin" for OpenStack Dashboard -
https://github.com/stackforge/savanna-dashboard
It doesn't contains any copy-paste and dependencies for Django/Horizon and
currently compatible with Grizzly and Havana OpenStack Dashboard, it only
contains our code and could be insta
I have a few questions left unanswered by the blueprint/wiki:
#1 - Should the true default configuration-group for a service-type be
customizable by the cloud provider?
#2 - Should a user be able to enumerate the entire actualized/realized
set of values for a configuration-group,
59 matches
Mail list logo
