Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 01/06/2016 11:48 AM, Dougal Matthews wrote: On 5 January 2016 at 17:09, Jiri Tomasek > wrote: On 12/23/2015 07:40 PM, Steven Hardy wrote: On Wed, Dec 23, 2015 at 11:05:05AM -0600, Ben Nemec wrote: On 12/23/2015

Re: [openstack-dev] in which function does neutronv2 assign IP address for instance?

张晨 wrote: hi everyone, i have a question for the neutron code in liberty: how does neutron assign IP address for instance? in nova.network, it seems that neutron sever gets a feasible ip from the DB pool, which looks like this:

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 5 January 2016 at 17:09, Jiri Tomasek wrote: > On 12/23/2015 07:40 PM, Steven Hardy wrote: > >> On Wed, Dec 23, 2015 at 11:05:05AM -0600, Ben Nemec wrote: >> >>> On 12/23/2015 10:26 AM, Steven Hardy wrote: >>> On Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec

[openstack-dev] in which function does neutronv2 assign IP address for instance?

hi everyone, i have a question for the neutron code in liberty: how does neutron assign IP address for instance? in nova.network, it seems that neutron sever gets a feasible ip from the DB pool, which looks like this: nova.compute.manager.ComputeVirtAPI._allocate_network_async() ->

Re: [openstack-dev] [heat] Client checking of server version

I ran into an issue in a review about moving environment resolution from client to server [1]. It revolves around clients being able to access older versions of servers (that's a pretty simplistic description; see [2] for the spec). Before the holiday, Steve Hardy and I were talking about the

Re: [openstack-dev] [doc] DocImpact vs. reno

On 2016-01-06 07:52:48 -0500 (-0500), Sean Dague wrote: [...] > I think auto openning against a project, and shuffling it to > manuals manually (with details added by humans) would be fine. > > It's not clear to me why a new job was required for that. The new check job was simply a requirement

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

On Tue, Jan 05, 2016 at 12:55:01PM (-0500), Emilien Macchi wrote: > Hi, > > Alex Schultz (mwhahaha on IRC) has been a very active contributor over > the last months in the Puppet OpenStack group: > * He's doing a lot of reviews and they are very valuable. He's in my > opinion fully aware of our

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

Hi, We would like to be notified once an alarm state is changed, so we prefer using the message bus. As far as I understand, ceilometer and aodh APIs do not provide immediate notifications. If we use the APIs, we will have to poll the data periodically and look for changes, and we will get

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

On 06/01/2016 8:11 AM, AFEK, Ifat (Ifat) wrote: Hi, We would like to be notified once an alarm state is changed, so we prefer using the message bus. As far as I understand, ceilometer and aodh APIs do not provide immediate notifications. If we use the APIs, we will have to poll the data

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 6 January 2016 at 12:30, Ryan Brown wrote: > On 12/23/2015 04:19 AM, Dougal Matthews wrote: > >> >> >> On 22 December 2015 at 17:59, Ben Nemec > > wrote: >> >> Can we just do git like I've been suggesting all

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/23/2015 04:19 AM, Dougal Matthews wrote: On 22 December 2015 at 17:59, Ben Nemec > wrote: Can we just do git like I've been suggesting all along? ;-) More serious discussion inline. :-) On 12/22/2015 09:36 AM, Dougal

Re: [openstack-dev] [ansible] tox functional testing rename

On 20 December 2015 at 19:24, Paul Belanger wrote: > > > I've proposed a series of patches[1] to rename tox -eansible-functional to > tox -efunctional. While the change is trival, it is meant to workaround an > interpreter issue with tox[2]. Additionally, the change brings

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Hi Jay, +1 on the lack of consistency between projects. When adding the generator to Neutron, we could not find a consistent pattern so we tried to adopt as best as possible. Let me know if you need any feedback on the Neutron experience. Regards, Martin From: "Jay S. Bryant"

[openstack-dev] [chef] deprecation and removal of old branches

Hi everybody, due to a hint on this patch https://review.openstack.org/#/c/264130/1 i walked through some of our cookbooks and found that we never actually deprecated or removed the old branches for most of our cookbooks. To do this, we just need to

Re: [openstack-dev] [doc] DocImpact vs. reno

On 01/05/2016 11:07 PM, Lana Brindley wrote: > >> On 6 Jan 2016, at 1:19 PM, Jeremy Stanley wrote: >> >> On 2016-01-06 11:43:34 +1100 (+1100), Lana Brindley wrote: >> [...] >>> I’m starting to think that DocImpact needs to simply be retired then >> >> Alternatively, let the

Re: [openstack-dev] [nova] [all] Excessively high greenlet default + excessively low connection pool defaults leads to connection pool latency, timeout errors, idle database connections / workers

Hi Mike, Thank you for this brilliant analysis! We've been seeing such timeout errors in downstream periodically and this is the first time someone has analysed the root cause thoroughly. On Fri, Dec 18, 2015 at 10:33 PM, Mike Bayer wrote: > Hi all - > > Let me start out with

Re: [openstack-dev] [openstack-ansible][designate] Regarding Designate install through Openstack-Ansible

Hi Swati, You're making good progress! I've reviewed 1 and it looks right. With regards to 2, it seems that according to [1] you need to run 'designate-manage database sync' after setting up the database. We have a similar pattern in [2] which you can model from. With regards to 4, the task

Re: [openstack-dev] [heat] Client checking of server version

On 01/05/2016 04:37 PM, Steven Hardy wrote: On Mon, Jan 04, 2016 at 03:53:07PM -0500, Jay Dobies wrote: I ran into an issue in a review about moving environment resolution from client to server [1]. It revolves around clients being able to access older versions of servers (that's a pretty

[openstack-dev] [nova] Next meeting is tomorrow 2100UTC

Hi, Just a reminder that we're alternating meetings [1] but since this week number is odd, the next meeting will be held on Thursday Jan 7th at 2100UTC. Explanations can be found here http://lists.openstack.org/pipermail/openstack-dev/2016-January/083216.html "Odd" and "Even" meetings will

Re: [openstack-dev] [doc] DocImpact vs. reno

On 01/06/2016 09:02 AM, Jeremy Stanley wrote: > On 2016-01-06 07:52:48 -0500 (-0500), Sean Dague wrote: > [...] >> I think auto openning against a project, and shuffling it to >> manuals manually (with details added by humans) would be fine. >> >> It's not clear to me why a new job was required

Re: [openstack-dev] [cinder][python-client-api] Retrieve host-name attribute of Cinder Volume

Sorry, of course this https://github.com/openstack/cinder/blob/master/cinder/volume/utils.py#L575 On Wed, Jan 6, 2016 at 5:57 PM, Yuriy Nesenenko wrote: > You can use this function > https://github.com/openstack/cinder/blob/master/cinder/volume/utils.py#L5 > > On Wed,

[openstack-dev] [cinder][python-client-api] Retrieve host-name attribute of Cinder Volume

Hello, >From CLI, I can see the host-name in the cinder show command as follows: | os-vol-host-attr:host | openstack4@mySCSIBackend#pool1 | How this info can be accessed from the cinder python client? I can access other information (id, size, name etc.) as follows: >>>

Re: [openstack-dev] [QA] No meetings for the next 2 weeks

On Thu, Dec 17, 2015 at 04:06:38PM -0500, Matthew Treinish wrote: > > Hi Everyone, > > As we discussed during today's QA meeting we'll not be holding the weekly QA > meeting for the next 2 weeks. Most people will be on vacation anyway, so this > likely isn't a big surprise. > > The next

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Hey Kendall, Sure. Count me in! :) Thanks,, Martin From: "Kendall J Nelson" To: "OpenStack Development Mailing List \(not for usage questions \)" Date: 06/01/2016 16:57 Subject:Re: [openstack-dev] [all]

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

I would like involvement in this discussion too from a documentation perspective... particularly maintaining the configuration reference and possibly standardizing how packagers include dynamic configuration files. On Wed, Jan 6, 2016 at 10:53 AM, Martin Hickey wrote:

[openstack-dev] [trove] Nominating Mariam John to Trove Core

Members of the Trove team, I would like to nominate Mariam John (johnma on IRC) to the Trove core review team. Mariam has been an active member of the Trove team for some time now. She added support for IBM DB2 in Trove and provided elements for building Trove guest images. She also

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Excerpts from Kendall J Nelson's message of 2016-01-05 13:48:46 -0600: > > Okay, to clarify, you are saying pip freeze to get the list of libraries > for the oslo.config.opts section in entry > points here https://github.com/openstack/cinder/blob/master/setup.cfg#L44 ? We do have a convention

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Excellent! I will get a proposal written up in the next few days here and I will include you both in it. If there is anyone else you know in other projects that might be interested as well, feel free to send them my way :) All the Best,

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Excerpts from Kendall J Nelson's message of 2016-01-05 13:52:10 -0600: > Hey Doug, > > To respond to your points :) > > 1. We are actually including the resulting opts.py file from > generate_cinder_opts.py so that deployers can distribute. That was added in > a subsequent patch- sorry for that

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Excerpts from Jay S. Bryant's message of 2016-01-05 13:55:30 -0600: > Ben, > > Please see my in-line responses ... > > On 01/04/2016 05:43 PM, Ben Nemec wrote: > > On 01/04/2016 03:50 PM, Kendall J Nelson wrote: > >> Hello, > >> > >> > >> In brainstorming ideas for talks at the upcoming summit,

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Hey Doug, This definitely sounds like something to look into. Would you be interested in being a part of a panel at the upcoming summit in Austin to discuss this? All the Best, Kendall J. Nelson

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Excerpts from Kendall J Nelson's message of 2016-01-06 13:07:30 -0600: > Hey Doug, > > This definitely sounds like something to look into. Would you be > interested in being a part of a panel at the upcoming summit in Austin to > discuss this? I'm not sure what you mean by "panel." Are you

Re: [openstack-dev] [cinder][python-client-api] Retrieve host-name attribute of Cinder Volume

Try client.volumes..get(id).__dict__[' *os-vol-host-attr:host'] * *Ugly, but it seems to work* On 6 January 2016 at 18:20, Pradip Mukhopadhyay wrote: > Thanks, Yuriy. > > My question was: how can I retrieve the "host@backend#pool" from the > pythonclient API of

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Yeah something like that- I'm new to the process so I may have the terminology wrong. So far I have Martin Hickey and Matt Kassawara and myself. I was hoping to get someone from Nova and maybe someone from Keystone as well. All the Best,

Re: [openstack-dev] [trove] Nominating Mariam John to Trove Core

Thanks for the nomination Amrith and I think Mariam will be a great addition to the core team. +1 -Craig On Jan 6, 2016, at 12:39 PM, Amrith Kumar > wrote: Members of the Trove team, I would like to nominate Mariam John (johnma on IRC) to the

[openstack-dev] [Nova] Next CellsV2 meeting is Jan 13 at 2100UTC

See subject :) As explained in http://lists.openstack.org/pipermail/openstack-dev/2016-January/083216.html a recurring calendar event based on alternating weeks will now be incorrect. I had to fix my calendar and I expect others will want to do the same.

[openstack-dev] [Designate] Old Reviews

Hi All, We have built up a lot of old reviews, that can be removed. So, this day next week I proposed I abandon any reviews that have not been updated in 42 days. If people want to Unabandon any changes, please do - this is not about In our repos the following list would be abandoned if there

Re: [openstack-dev] [Horizon] Updating XStatic packages

I did update some of the low hanging packages where the upgrades seemed safe to do and noted the patch numbers in the same EtherPad. I wasn't sure what to mark the effort against. So I created some bugs. Should it be a blueprint? -Rajat On Wed, Jan 6, 2016 at 2:18 AM, Rob Cresswell (rcresswe)

Re: [openstack-dev] [puppet] [neutron] Serious bug in puppet neutron cli json output parsing.

Mike Dorman writes: > I wonder if we should just refactor the Neutron provider to support > either format? That way we stay independent from whatever the > particular installation’s cliff/tablib situation is. > > We can probably safely assume that none of the Neutron objects

Re: [openstack-dev] [cinder][python-client-api] Retrieve host-name attribute of Cinder Volume

Thanks, Yuriy. My question was: how can I retrieve the "host@backend#pool" from the pythonclient API of volume listing? Once I have that, I should use this method to extract the pool-name. But how can I access this info? CLI is showing this as in the following field:

Re: [openstack-dev] [chef] deprecation and removal of old branches

I'm +1 on this idea. Looking at other OpenStack projects (Nova, Neutron, etc.) on GitHub, they only have stable/liberty and stable/kilo, with anything older dropped. We're already following this support model, so I think the cleanup should happen, that way there isn't any ambiguity on which

Re: [openstack-dev] [heat] Client checking of server version

On 06/01/16 08:53, Jay Dobies wrote: I ran into an issue in a review about moving environment resolution from client to server [1]. It revolves around clients being able to access older versions of servers (that's a pretty simplistic description; see [2] for the spec). Before the holiday, Steve

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

Hey Martin, I thought it might be interesting to get a panel discussion at the Summit to discuss the lack of consistency/ work towards a more universal way of using the oslo config generator. Would you be interested? I was hoping to get someone from Neutron, Nova and Keystone and I could

Re: [openstack-dev] [heat] Client checking of server version

On 05/01/16 16:37, Steven Hardy wrote: On Mon, Jan 04, 2016 at 03:53:07PM -0500, Jay Dobies wrote: I ran into an issue in a review about moving environment resolution from client to server [1]. It revolves around clients being able to access older versions of servers (that's a pretty simplistic

[openstack-dev] [QA] Mitaka Code Sprint

Hi Everyone, As we've done the past 2 cycles we'll be having another QA code sprint this cycle. I've felt these sprints have been very effective in the past and helped us make good progress on several work items in a short amount of time, so I think having another sprint will work well again for

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

+1 On 01/05/2016 06:55 PM, Emilien Macchi wrote: > Hi, > > Alex Schultz (mwhahaha on IRC) has been a very active contributor over > the last months in the Puppet OpenStack group: > * He's doing a lot of reviews and they are very valuable. He's in my > opinion fully aware of our conventions and

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

Hi Ifat, what way do you want to use the alarm change notifications? using events from Ceilometer API or directly collecting the notifications from message bus? if we configure Ceilometer to listen the notifications from aodh, the notifications about alarm changes will be converted to events

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

Emilien Macchi wrote: > Hi, > > Alex Schultz (mwhahaha on IRC) has been a very active contributor over > the last months in the Puppet OpenStack group: > * He's doing a lot of reviews and they are very valuable. He's in my > opinion fully aware of our conventions and has nice insights to improve

Re: [openstack-dev] [nova] [all] Excessively high greenlet default + excessively low connection pool defaults leads to connection pool latency, timeout errors, idle database connections / workers

On 01/06/2016 09:11 AM, Roman Podoliaka wrote: > Hi Mike, > > Thank you for this brilliant analysis! We've been seeing such timeout > errors in downstream periodically and this is the first time someone > has analysed the root cause thoroughly. > > On Fri, Dec 18, 2015 at 10:33 PM, Mike Bayer

[openstack-dev] [trove] Adding support for HBase in Trove

TL;DR Should Trove treat HBase as a special database because one use case is as part of a large multi-node Hadoop cluster, and therefore either not support it at all, or necessarily use Sahara to provision and manage a cluster? There are pro's and con's and it is argued that the con's outweigh

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

On Wed, Jan 6, 2016 at 4:40 PM, Emilien Macchi wrote: > > > On 01/05/2016 12:55 PM, Emilien Macchi wrote: >> Hi, >> >> Alex Schultz (mwhahaha on IRC) has been a very active contributor over >> the last months in the Puppet OpenStack group: >> * He's doing a lot of reviews and

Re: [openstack-dev] [trove] Adding support for HBase in Trove

just my 2 cents... I think you can do both. The great thing about Trove is that its providing an abstract api so users just deal with provisioning db's, scaling db's, etc. Having a simple plugin that doesn't depend on all of Sahara, for the case a user only wants a single node HBase does make

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

Congrats Alex! :D 2016-01-06 20:59 GMT-03:00 Alex Schultz : > On Wed, Jan 6, 2016 at 4:40 PM, Emilien Macchi wrote: > > > > > > On 01/05/2016 12:55 PM, Emilien Macchi wrote: > >> Hi, > >> > >> Alex Schultz (mwhahaha on IRC) has been a very active

Re: [openstack-dev] [Neutron] Gate failure

Ugh, this test is racey. I should have paid closer attention before I +2'ed, my bad. It just iterates external ports and uses an IP not in that list so if another test grabbed the same IP, the floating IP creation request specifying that IP will fail. Revert proposed here:

[openstack-dev] [QA] Meeting Thursday January 7th at 9:00 UTC

Hi everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, January 7th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

Re: [openstack-dev] [Neutron] Gate failure

On Wed, Jan 6, 2016, at 08:48 PM, Henry Gessau wrote: > Armando M. wrote: > > Hi folks, > > > > Due to [1], Neutron related jobs (api, and lbaas) are failing. Please hold > > your +A button until the issue is resolved. > > > > Thanks, > > Armando > > > > [1]

Re: [openstack-dev] [QA] Meeting Thursday January 7th at 9:00 UTC

Sorry, as http://lists.openstack.org/pipermail/openstack-dev/2016-January/083397.html the next meeting should be scheduled at 1700 UTC, not 0900 UTC. Thanks 2016-01-07 11:27 GMT+09:00 Ken'ichi Ohmichi : > Hi everyone, > > Please reminder that the weekly OpenStack QA team

[openstack-dev] [neutron][gate] neutron-dvsm-api gate failures

Hi All, Not sure if this already is being looked into. neutron-dvsm-api gate has been failing consistently offlate. The only test failing in the gate is neutron.tests.api.admin.test_floating_ips_admin_actions.FloatingIPAdminTestJSON. test_create_floatingip_with_specified_ip_address There are

[openstack-dev] [openstacksdk][nose] Namespace conflict?

Hi, We have been using python-openstacksdk for some time, so far so good. Just encountered a problem when running latest devstack environment. The error looks something like: $ python testsdk.py Traceback (most recent call last): File "testsdk.py", line 2, in from openstack import profile

Re: [openstack-dev] [chef] deprecation and removal of old branches

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 1/6/16 10:22 AM, Samuel Cassiba wrote: > I'm +1 on this idea. Looking at other OpenStack projects (Nova, Neutron, > etc.) on GitHub, they only have stable/liberty and stable/kilo Sounds good to me too. - -- Best Regards, JJ Asghar c:

Re: [openstack-dev] [cinder][python-client-api] Retrieve host-name attribute of Cinder Volume

Thanks a ton Duncan. It's just awesome. >>> volumes[0].__dict__['os-vol-host-attr:host'] u'openstack4@cmodeSCSIBackend#pool1' >>> --pradip On Thu, Jan 7, 2016 at 12:53 AM, Duncan Thomas wrote: > Try client.volumes..get(id).__dict__[' > > *os-vol-host-attr:host'] *

Re: [openstack-dev] [trove] Adding support for HBase in Trove

Kevin Fox writes: > as far as that plugin ever should go. If you need scale up/down, etc, then > your starting to reimplement large swaths of Sahara, and like the Cinder > plugin for Nova, there could be a plugin that works identically to the stand > alone one that converts the same api over to a

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

Hi Ifat, I meant new API to get statistcs on events data, like "statistics" API on samples data, that has been discussed but not implemented yet. because I thought you'd like to use events data about alarm changes. if you want to directly use the notification messages just because you want

Re: [openstack-dev] [Horizon] naming of Javascript bits

Richard My preference is the same as what you've got there. Fully namespaced Services and Controller allow for better reusability and possibly maintainability. If all "deleteService" were named just that, it'll be mighty confusing to use it in other places. With regards to tying the folder path

[openstack-dev] [horizon][help][angularjs] facing issue with my angularjs patch

Hello All, I am I am adding QoS panel in angularjs. i have submitted a patch for adding panel with delete action button in this patch https://review.openstack.org/#/c/247997/ it is working as expected. over that i have added for edit QoS policy action in this patch

Re: [openstack-dev] [Neutron] Gate failure

Ah, that was a bit misleading. We're not leaking any floating IPs. The create method for them adds them to a list that is cleaned up on teardown. The issue was that the get_unused_ip method was iterating over v4 and v6 subnets. So if it happened to pick a v6 subnet, it would cause the test to

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

On 01/05/2016 12:55 PM, Emilien Macchi wrote: > Hi, > > Alex Schultz (mwhahaha on IRC) has been a very active contributor over > the last months in the Puppet OpenStack group: > * He's doing a lot of reviews and they are very valuable. He's in my > opinion fully aware of our conventions and has

Re: [openstack-dev] [trove] Nominating Mariam John to Trove Core

I agree! +1 Peter -Original Message- From: Vyvial, Craig [mailto:craig.vyv...@hpe.com] Sent: January-06-16 2:40 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [trove] Nominating Mariam John to Trove Core Thanks for the nomination

[openstack-dev] [release][stable][nova] python-novaclient release 2.23.3 (kilo)

We are delighted to announce the release of: python-novaclient 2.23.3: Client library for OpenStack Compute API This release is part of the kilo stable release series. With source available at: https://git.openstack.org/cgit/openstack/python-novaclient With package available at:

Re: [openstack-dev] [heat] Client checking of server version

On 01/06/2016 12:05 PM, Zane Bitter wrote: On 05/01/16 16:37, Steven Hardy wrote: On Mon, Jan 04, 2016 at 03:53:07PM -0500, Jay Dobies wrote: I ran into an issue in a review about moving environment resolution from client to server [1]. It revolves around clients being able to access older

Re: [openstack-dev] [neutron][networking-sfc] API clarification questions

On 10/28/2015 04:14, Giuseppe (Pino) de Candia wrote: On Wed, Oct 28, 2015 at 4:20 PM, Russell Bryant > wrote: I read through the proposed SFC API here: http://docs.openstack.org/developer/networking-sfc/api.html We have similarly

[openstack-dev] [heat-translator][tacker] Etherpad for TOSCA NFV to Heat translation

I created an Etherpad [1] to discuss the mapping of TOSCA NFV objects [2] to Heat resources by heat-translator, in support of this [3] blueprint. The related tosca-parser work [4][5] is finishing up, so the next step is to map these objects into Heat resources. This will likely be a

Re: [openstack-dev] [Nova] Next CellsV2 meeting is Jan 13 at 2100UTC

On Jan 6, 2016, at 11:41, Andrew Laski wrote: > As explained in > http://lists.openstack.org/pipermail/openstack-dev/2016-January/083216.html a > recurring calendar event based on alternating weeks will now be incorrect. I > had to fix my calendar and I expect others will

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

Hi, Alex is doing great job! +1 from my side! 2016-01-06 16:27 GMT+03:00 Sebastien Badia : > On Tue, Jan 05, 2016 at 12:55:01PM (-0500), Emilien Macchi wrote: > > Hi, > > > > Alex Schultz (mwhahaha on IRC) has been a very active contributor over > > the last months in the Puppet

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

When you state Swift I assume you mean TripleO will use swift APIs to access objects in it (template, metadata, etc). There are many environment where there is no swift but Ceph or other object store that can be used for it using swift APIs. Are all these will be under single user/project that