On Tue, Aug 09, 2016 at 09:16:02PM -0700, John Griffith wrote:
> Sorry, I wasn't a part of the sessions in Austin on the topic of long
> terms support of Cinder drivers. There's a lot going on during the summits
> these days.
For the record the session in Austin, that I think Matt was
On Tue, Aug 9, 2016 at 10:26 PM, Matthew Treinish
wrote:
> On Tue, Aug 09, 2016 at 09:16:02PM -0700, John Griffith wrote:
> > On Tue, Aug 9, 2016 at 7:21 PM, Matthew Treinish
> > wrote:
> >
> > > On Tue, Aug 09, 2016 at 05:28:52PM -0700, John Griffith
hi Armando
I think this feature causes problem in sriov scenario, since sriov NIC
don't support the vf has the same mac,even the port belongs to the different
network.
发自网易邮箱手机版
On 2016-08-10 04:55 , Armando M. Wrote:
On 9 August 2016 at 13:53, Anil Rao
On Tue, Aug 09, 2016 at 09:16:02PM -0700, John Griffith wrote:
> On Tue, Aug 9, 2016 at 7:21 PM, Matthew Treinish
> wrote:
>
> > On Tue, Aug 09, 2016 at 05:28:52PM -0700, John Griffith wrote:
> > > On Tue, Aug 9, 2016 at 4:53 PM, Sean McGinnis
> >
On Tue, Aug 9, 2016 at 7:21 PM, Matthew Treinish
wrote:
> On Tue, Aug 09, 2016 at 05:28:52PM -0700, John Griffith wrote:
> > On Tue, Aug 9, 2016 at 4:53 PM, Sean McGinnis
> wrote:
> >
> > > .
> > > >
> > > > Mike, you must have left the midcycle by
On Wed, Aug 10, 2016 at 01:39:55AM +, Jeremy Stanley wrote:
> So I guess what I'm asking: If stable branches exist as a place for
> package maintainers to collaborate on a common set of backported
> fixes, and are not actually usable to that end, why do we continue
> to provide them?
I don't
Hi Sridhar,
You said in https://review.openstack.org/#/c/255146/ we should not expose the
infra_driver and mgmt_driver to user,but they have been already exposed by API
at
https://github.com/openstack/tacker/blob/master/tacker/extensions/vnfm.py#L205,
so what do you think?Do we need remove the
On Tue, Aug 09, 2016 at 10:21:19PM -0400, Matthew Treinish wrote:
> I fully understood the proposal but I still think you're optimizing for the
> wrong thing. We have a community process for doing backports and maintaining
> released versions of OpenStack code. The fundamental problem here is
Hi all,
The default tenant_network_types is geneve, after installed following this
document http://docs.openstack.org/developer/networking-ovn/testing.html
```
[ml2]
tenant_network_types = geneve
extension_drivers = port_security
type_drivers = local,flat,vlan,geneve
```
To enable vxlan, I
Hi,
The issue still exists after the https://review.openstack.org/352490
merged, what else should I do?
http://logs.openstack.org/58/351458/8/check/gate-python-bileanclient-requirements/fa1119c/console.html
-- Original --
From: "Jeremy
On Wed, Aug 10, 2016 at 01:39:55AM +, Jeremy Stanley wrote:
> On 2016-08-09 15:56:57 -0700 (-0700), Mike Perez wrote:
> > As others have said and as being a Cinder stable core myself, the status-quo
> > and this proposal itself are terrible practices because there is no testing
> > behind it,
On Tue, Aug 09, 2016 at 05:28:52PM -0700, John Griffith wrote:
> On Tue, Aug 9, 2016 at 4:53 PM, Sean McGinnis wrote:
>
> > .
> > >
> > > Mike, you must have left the midcycle by the time this topic came
> > > up. On the issue of out-of-tree drivers, I specifically offered
Hi,
We have weekly Nova API meeting today. The meeting is being held Wednesday
UTC1300 and irc channel is #openstack-meeting-4.
The proposed agenda and meeting details are here:
https://wiki.openstack.org/wiki/Meetings/NovaAPI
Please feel free to add items to the agenda.
Thanks
hi, all.
I have faced some strange problems when getting LBaaS resources, such
as loadbalancers, listeners, pools, etc.
For example, when I send a request which only filtering "id" attribute,
like this:
>>> curl -g -i -X GET
http://10.0.44.233:9696/v2.0/lbaas/listeners.json?fields=id \
On 2016-08-09 15:56:57 -0700 (-0700), Mike Perez wrote:
> As others have said and as being a Cinder stable core myself, the status-quo
> and this proposal itself are terrible practices because there is no testing
> behind it, thereby it not being up to the community QA standards set.
[...]
In
On 08/09/2016 06:00 PM, Zane Bitter wrote:
In either case a good mechanism might be to use a Heat Software
Deployment via the Heat API directly (i.e. not as part of a stack) to
push changes to the servers. (I say 'push' but it's more a case of
making the data available for os-collect-config
On Tue, Aug 9, 2016 at 4:53 PM, Sean McGinnis wrote:
> .
> >
> > Mike, you must have left the midcycle by the time this topic came
> > up. On the issue of out-of-tree drivers, I specifically offered this
> > proposal (a community managed mechanism for distributing driver
>
On Tue, Aug 09, 2016 at 10:19:04PM +0100, JP Maxwell wrote:
> There is only currently one issue: I can get it to authenticate against
> login.ubuntu but neither dev or production OpenStackID. If we wish to
> stand
> this up against OpenStackID I'm going to need some eyes on
.
>
> Mike, you must have left the midcycle by the time this topic came
> up. On the issue of out-of-tree drivers, I specifically offered this
> proposal (a community managed mechanism for distributing driver
> bugfix backports) as an compromise alternative to try to address the
> needs of both
On 08/09/2016 06:56 PM, Mike Perez wrote:
On 10:31 Aug 06, Sean McGinnis wrote:
I'm open and welcome to any feedback on this. Unless there are any major
concerns raised, I will at least instruct any Cinder stable cores to
start allowing these bugfix patches through past the security only
On Tue, Aug 09, 2016 at 03:56:57PM -0700, Mike Perez wrote:
> If you want to change that, work with the stable team on the various options
> provided. This tangent of people whining on the mailing list and in
> #openstack-cinder is not going to accomplish anything.
That's what we're doing here
On 08/09/2016 05:45 PM, Mike Perez wrote:
On 19:40 Aug 08, Duncan Thomas wrote:
On 8 August 2016 at 18:31, Matthew Treinish wrote:
This argument comes up at least once a cycle and there is a reason we
don't do
this. When we EOL a branch all of the infrastructure for
TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll be
missed. :-)
A few notes following up on Matt Riedemann, Clint Byrum, Daniel Berrange’s
conversation regarding the Nova mascot…
Nova doesn’t have to have a mascot if the majority of the team doesn’t want
one. I’m not
Thanks Armando.
-Anil
From: Armando M. [mailto:arma...@gmail.com]
Sent: Tuesday, August 09, 2016 1:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Neutron Port MAC Address Uniqueness
On 9 August 2016 at 13:53, Anil Rao
On 10:31 Aug 06, Sean McGinnis wrote:
> I'm open and welcome to any feedback on this. Unless there are any major
> concerns raised, I will at least instruct any Cinder stable cores to
> start allowing these bugfix patches through past the security only
> phase.
As others have said and as being a
On Tue, Aug 09, 2016 at 03:14:43PM -0400, Davanum Srinivas wrote:
> +1 for volunteers to step up.
I'll do it and I have a *very* basic prototype done. It wont be in Newton
though. Having said that if there is another volenteer I'm happy to work with
them or free up time :)
Yours Tony.
PS:
It needs to work in a distributed way...
What happens if the one node you have cron running on doesn't work for a while.
Keystone breaks?
If the undercloud deploys a timed workfow where the workflow can fail over from
machine to machine, that would work.
Thanks,
Kevin
Thanks Kris, "StandardOutput=null" did the trick.
Besides, this post (http://www.kibinlabs.com/systemd-logging-tricks/)
treats nova-compute as a "bad daemon" :=(
On Tue, Aug 9, 2016 at 7:05 PM, Kris G. Lindgren
wrote:
> Systemd logs all python output by default, if you
Systemd logs all python output by default, if you have rsyslog to pull from the
systemd as well you can get double logging. I think you need to execute under
systemd with: StandardOutput=null in the unit file under the [service]
heading. Atleast that’s what we do.
Disclaimer: we don’t run
On 09/08/16 17:11, Adam Young wrote:
The Fernet token format uses a symmetric key to sign tokens. In order
to check the signature, these keys need to be synchronized across all of
the Keystone servers.
I don't want to pass around nake symmetric keys. The right way to do
this is to put them
All,
In the previous e-mail, [1] was recommending 3rd party ci to pin zuul to v.
2.1.0, but this has pip dependency conflicts with nodepool 0.3.0 when installed
on the same VM (common case typical for 3rd party ci) causing zuul service to
fail to start.
This is fixed by using the newly created
Hi guys,
We want to be able to forward nova-compute's log to a central rsyslog but
at the same time mantain the local "/var/log/nova/nova-compute.log". In
Icehouse we achieved this with the following configuration in
"/etc/rsyslog.d/60-nova.conf":
*.*;local0.none,auth,authpriv.none
On 19:40 Aug 08, Duncan Thomas wrote:
> On 8 August 2016 at 18:31, Matthew Treinish wrote:
>
> >
> > This argument comes up at least once a cycle and there is a reason we
> > don't do
> > this. When we EOL a branch all of the infrastructure for running any ci
> > against
>
On 07/08/16 19:52, Clint Byrum wrote:
Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200:
On 05/08/16 21:48, Ricardo Rocha wrote:
Hi.
Quick update is 1000 nodes and 7 million reqs/sec :) - and the number
of requests should be higher but we had some internal issues. We have
a
The Fernet token format uses a symmetric key to sign tokens. In order
to check the signature, these keys need to be synchronized across all of
the Keystone servers.
I don't want to pass around nake symmetric keys. The right way to do
this is to put them into a PKCS 11 Envelope. Roughly,
On 08/09/2016 02:10 PM, Ben Swartzlander wrote:
The best example of why this is good is Linux. If you tell the Linux people to
take their drivers out of the tree I can guarantee you they'll laugh you out of
the room. The reasons for their stance are many and I won't recount them here
(unless
On 9 August 2016 at 13:53, Anil Rao wrote:
> Is the MAC address of a Neutron port on a tenant virtual network globally
> unique or unique just within that particular tenant network?
>
The latter:
Is the MAC address of a Neutron port on a tenant virtual network globally
unique or unique just within that particular tenant network?
Thanks,
Anil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 08/09/2016 11:52 AM, Ihar Hrachyshka wrote:
Walter A. Boring IV wrote:
On 08/08/2016 02:28 PM, Ihar Hrachyshka wrote:
Duncan Thomas wrote:
On 8 August 2016 at 21:12, Matthew Treinish
wrote:
Ignoring all that, this
On Tue, Aug 9, 2016 at 10:00 PM, Clint Byrum wrote:
> Excerpts from Ricardo Rocha's message of 2016-08-08 11:51:00 +0200:
>> Hi.
>>
>> On Mon, Aug 8, 2016 at 1:52 AM, Clint Byrum wrote:
>> > Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200:
>>
ok so for now I remove database cleanup and added Sean Dague/Nova to that
slot
On Tue, Aug 9, 2016 at 3:21 PM, Chris Morgan wrote:
> Yeah we dropped that in but colored it orange meaning not many +1s and
> quite a narrow topic in context
>
> On Tue, Aug 9, 2016 at 3:11 PM,
But If I use statsd logs then I won't have an opportunity to choose which
stats I want to send. Also I will not have an ability to change the name of
stats. I want to have some ability to use the simple script on each swift
node which will get stats throug the cli and send it to OpenTSDB.
On Tue,
Sean has done a fantastic job on the BiFrost work and kolla-host work. What is
needed is the last step - which is a final thorough technical review from the
core review team so we can get it merged by end of week. If your struggling to
find the work in the review queue, use this link:
On 08/09/2016 03:01 PM, Ihar Hrachyshka wrote:
Walter A. Boring IV wrote:
I think "currently active stable branches" is key there. These branches
would no longer be "currently active". They would get an EOL tag
when it
reaches the end of the support phases. We just
Since upgrading to liberty, we've noticed some very dramatic lags in the
application of security group updates. Experience shows that it takes
somewhere between 15 minutes and forever for changes to take effect.
For example, I just now added a source group rule to a project:
Ingress -
Excerpts from Ricardo Rocha's message of 2016-08-08 11:51:00 +0200:
> Hi.
>
> On Mon, Aug 8, 2016 at 1:52 AM, Clint Byrum wrote:
> > Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200:
> >> On 05/08/16 21:48, Ricardo Rocha wrote:
> >> > Hi.
> >> >
> >> > Quick
Hello Everyone,
On behalf of the TOSCA-Parser team, I am pleased to announce the 0.6.0
PyPI release of tosca-parser which can be downloaded from
https://pypi.python.org/pypi/tosca-parser
This release includes following enhancements:
Python 3.5 support
Support for TOSCA Repository which is an
On 09/08/2016 19:58, Ihar Hrachyshka wrote:
> Walter A. Boring IV wrote:
>
>> On 08/08/2016 02:28 PM, Ihar Hrachyshka wrote:
>>> Duncan Thomas wrote:
>>>
On 8 August 2016 at 21:12, Matthew Treinish wrote:
Ignoring
Yeah we dropped that in but colored it orange meaning not many +1s and
quite a narrow topic in context
On Tue, Aug 9, 2016 at 3:11 PM, Matt Fischer wrote:
> I didn't see any plus ones on my idea for the db cleanup session so if we
> need to drop it to fit something that
+1 for volunteers to step up.
-- Dims
On Tue, Aug 9, 2016 at 3:07 PM, Doug Hellmann wrote:
> Excerpts from John Dickinson's message of 2016-08-09 11:14:57 -0700:
>> I'd like to advocate for *not* raising minimum versions very often. Every
>> time some OpenStack project
Excerpts from Hayes, Graham's message of 2016-08-09 18:54:57 +:
> On 09/08/2016 19:41, John Dickinson wrote:
> >
> >
> > On 9 Aug 2016, at 11:33, Ian Cordasco wrote:
> >
> >>
> >>
> >> -Original Message-
> >> From: John Dickinson
> >> Reply: OpenStack Development Mailing
I didn't see any plus ones on my idea for the db cleanup session so if we
need to drop it to fit something that works for me.
On Aug 9, 2016 12:29 PM, "Chris Morgan" wrote:
> WG6, day one? That's 40 minutes. Would run alongside Large Deployment.
> Currently that has the
Excerpts from John Dickinson's message of 2016-08-09 11:14:57 -0700:
> I'd like to advocate for *not* raising minimum versions very often. Every
> time some OpenStack project raises minimum versions, this change is
> propagated to all projects, and that puts extra burden on anyone who is
>
Hi All -
Apologies, our dual-redundant co-chair strategy has failed, as I’m on vacation
and Blair has taken ill. Unfortunately we shall need to cancel our meeting for
later today and hope to come back stronger next week.
Apologies for the short notice,
Stig
On 08/09/2016 01:37 PM, John Dickinson wrote:
> In that case, they are still co-installable, because the nova minimum
> satisfies both.
The requirements project currently advocates the use of
upper-requirements.txt as what is targeted for packagers. This is
what's tested.
--
-- Matthew Thode
Walter A. Boring IV wrote:
I think "currently active stable branches" is key there. These branches
would no longer be "currently active". They would get an EOL tag when it
reaches the end of the support phases. We just wouldn't delete the
branch.
This argument comes up
On 09/08/2016 19:41, John Dickinson wrote:
>
>
> On 9 Aug 2016, at 11:33, Ian Cordasco wrote:
>
>>
>>
>> -Original Message-
>> From: John Dickinson
>> Reply: OpenStack Development Mailing List (not for usage questions)
>>
>> Date: August
Walter A. Boring IV wrote:
On 08/08/2016 02:28 PM, Ihar Hrachyshka wrote:
Duncan Thomas wrote:
On 8 August 2016 at 21:12, Matthew Treinish wrote:
Ignoring all that, this is also contrary to how we perform testing in
On Tue, Aug 09, 2016 at 01:14:24PM -0400, James Slagle wrote:
> I've proposed:
> https://review.openstack.org/353019
>
> which makes gate-tripleo-ci-centos-7-nonha-multinode-nv and
> gate-tripleo-ci-centos-7-undercloud-nv become voting jobs.
>
> I think these jobs have proven to be stable enough
On 9 Aug 2016, at 11:33, Ian Cordasco wrote:
>
>
> -Original Message-
> From: John Dickinson
> Reply: OpenStack Development Mailing List (not for usage questions)
>
> Date: August 9, 2016 at 13:17:08
> To: OpenStack Development
-Original Message-
From: John Dickinson
Reply: OpenStack Development Mailing List (not for usage questions)
Date: August 9, 2016 at 13:17:08
To: OpenStack Development Mailing List
Subject: Re:
fyi, Just so you all know. It's upper-constraints.txt. Note the word "upper" :)
-- Dims
On Tue, Aug 9, 2016 at 2:25 PM, Julien Danjou wrote:
> On Tue, Aug 09 2016, John Dickinson wrote:
>
>> I'd like to advocate for *not* raising minimum versions very often. Every
>> time
WG6, day one? That's 40 minutes. Would run alongside Large Deployment.
Currently that has the main room. Would nova be more universal to operators?
On Tue, Aug 9, 2016 at 1:57 PM, Tom Fifield wrote:
> Good news! Sean Dague is coming to the event and has volunteered to lead a
On Tue, Aug 09 2016, John Dickinson wrote:
> I'd like to advocate for *not* raising minimum versions very often. Every time
> some OpenStack project raises minimum versions, this change is propagated to
> all projects, and that puts extra burden on anyone who is maintaining packages
> and
I'd like to advocate for *not* raising minimum versions very often. Every time
some OpenStack project raises minimum versions, this change is propagated to
all projects, and that puts extra burden on anyone who is maintaining packages
and dependencies in their own deployment. If one project
Good news! Sean Dague is coming to the event and has volunteered to lead
a session on behalf of the nova team.
They're going to work on a list of questions that nova would like to ask
nova ops and also keep it open for general feedback.
Let's find a slot?
On 廿十六年八月八日 暮 02:18, Chris Morgan
On Wed, Aug 3, 2016 at 1:22 AM, zhuna wrote:
> Hi Carl,
>
>
>
> IMO, if the upstream router has the route to floating ip subnet, no need
> to assign additional IP address to the router.
>
>
>
> For example, there are 2 subnets in external network,
>
> Subnet1: 10.0.0.0/24
On Tue, Aug 9, 2016 at 1:30 PM, Michele Baldessari wrote:
> Hi James,
>
> On Tue, Aug 09, 2016 at 01:14:24PM -0400, James Slagle wrote:
>> I've proposed:
>> https://review.openstack.org/353019
>>
>> which makes gate-tripleo-ci-centos-7-nonha-multinode-nv and
>>
Hi,
Today Puppet OpenStack CI is running unit and functional test jobs
against puppet 3 and puppet 4.
Unit jobs for puppet 4 are currently voting and pretty stable.
Functional jobs for puppet 4 are not voting but also stable.
Even if Puppet4 has not been largely adopted by our community [1] yet,
On 08/08/2016 02:28 PM, Ihar Hrachyshka wrote:
Duncan Thomas wrote:
On 8 August 2016 at 21:12, Matthew Treinish
wrote:
Ignoring all that, this is also contrary to how we perform testing in
OpenStack.
We don't turn off entire classes of testing
I think "currently active stable branches" is key there. These branches
would no longer be "currently active". They would get an EOL tag when it
reaches the end of the support phases. We just wouldn't delete the
branch.
This argument comes up at least once a cycle and there is a reason we
Hi Melvin,
The OpenStack UX project just completed a study to understand operator
information needs including documentation, IRC, email lists and reviewing the
actual code. We were planning to briefly touch on the results (< 10 min), but
wanted to use the majority of the time to brainstorm
On Tue, Aug 9, 2016 at 1:14 PM, James Slagle wrote:
> I've proposed:
> https://review.openstack.org/353019
>
> which makes gate-tripleo-ci-centos-7-nonha-multinode-nv and
> gate-tripleo-ci-centos-7-undercloud-nv become voting jobs.
>
> I think these jobs have proven to be
Hi James,
On Tue, Aug 09, 2016 at 01:14:24PM -0400, James Slagle wrote:
> I've proposed:
> https://review.openstack.org/353019
>
> which makes gate-tripleo-ci-centos-7-nonha-multinode-nv and
> gate-tripleo-ci-centos-7-undercloud-nv become voting jobs.
definitely +1 for the
I've proposed:
https://review.openstack.org/353019
which makes gate-tripleo-ci-centos-7-nonha-multinode-nv and
gate-tripleo-ci-centos-7-undercloud-nv become voting jobs.
I think these jobs have proven to be stable enough that we can promote
them to be voting. If you have concerns, please vote on
I'm not quite sure but actually Liberty branch is open only for critical
and security issues right now, so I think that we can't include that to
liberty branch right now. Manual patching I think is best option for you, I
think.
On Tue, Aug 9, 2016 at 6:15 PM, Jeremy Freudberg
Hello team,
The IRC meeting this week (8/10) is canceled.
Thank you
Bin
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Update Aug 9th:
We are on scenario two: 3 control, 20 storage, 100 compute with Ceph.
Notes are now being collected in
https://review.openstack.org/#/c/352101/ along with tempest/rally results.
-Paul
On 05/08/16 17:48, Paul Bourke wrote:
Hi Kolla,
Thought it will be helpful to send a
Hi,
In consultation with Jeremy and some other Zuul contributors, I
have established the #zuul channel on Freenode. As intensive
development of Zuulv3 gets underway, this is a place where folks
working on that effort can discuss details without being
overwhelmed by the traffic in
Hiya,
I added a note to the documentation session, but noticed it had disappeared a
few hours later. I just was curious to know whether it was deleted or somehow
wasn’t saved to the etherpad.
Is deleting other folks comments fair game? I would hope they would be
crossed-out with a comment
On Tue, Aug 09, 2016 at 11:26:21AM -0500, Matt Riedemann wrote:
> On 8/8/2016 4:10 PM, Clint Byrum wrote:
> > Excerpts from Matt Riedemann's message of 2016-08-08 14:35:12 -0500:
> > > Not to be a major curmudgeon but I think we'd basically decided at the
> > > midcycle (actually weeks before)
Any way we could get the stats you need upstream in swift (emitted via statsd)
and then use something like
https://github.com/danslimmon/statsd-opentsdb-backend to get it in to opentsdb?
--John
On 9 Aug 2016, at 8:59, Alexandr Porunov wrote:
> Hello,
>
> I need to collect different metrics
On 8/8/2016 4:10 PM, Clint Byrum wrote:
Excerpts from Matt Riedemann's message of 2016-08-08 14:35:12 -0500:
Not to be a major curmudgeon but I think we'd basically decided at the
midcycle (actually weeks before) that Nova wasn't doing the mascot thing.
Could you maybe summarize the reason
-Original Message-
From: Sean Dague
Reply: OpenStack Development Mailing List (not for usage questions)
Date: August 9, 2016 at 11:21:47
To: openstack-dev@lists.openstack.org
Subject: Re:
Honestly, I don't think it matters what we use in our specifications, since
specifications are not public documents. Personally, in specifications, I am
fine with any of the proposed because they are all understandable! IF we have
to decide on something or if we want some preferred ways, then
On 08/09/2016 11:25 AM, Matthew Thode wrote:
> On 08/09/2016 10:22 AM, Ian Cordasco wrote:
>> -Original Message-
>> From: Matthew Thode
>> Reply: prometheanf...@gentoo.org , OpenStack
>> Development Mailing List (not for usage
On Mon, 8 Aug 2016 at 18:19 Ryan Beisner wrote:
> Greetings,
>
> I would like to nominate David Ames for addition to the
> charms-release team, as he has played a valuable role in the charm release
> processes. This change will grant privileges such as new stable
On 08/09/2016 04:28 AM, Vasyl Saienko wrote:
Hello Ironic'ers!
We've recorded a demo that shows how static portgroup works at the moment:
Flat network scenario: https://youtu.be/vBlH0ie6Lm4
Multitenant network scenario: https://youtu.be/Kk5Cc_K1tV8
Just watched both the above demo videos.
Hello,
I need to collect different metrics from swift servers and store those
metrics into OpenTSDB.
I found that there is way to collect metrics with statsd and graphite but
it isn't suitable for me because I have to store metrics into OpenTSDB.
Is there any way to store metrics from openstack
Hi everybody,
As a community we've decided we want to change the name of the project.
We felt that the name wasn't distinctive enough and might cause
confusion when looking for the project.
It was a long process but we've decide on the name Karbor.
Please bear with us while we move things around.
Hi All,
Unfortunately I have to attend another event tomorrow morning, so we
will cancel the next meeting and resume in two weeks. :)
If you have time between now and the next meeting, please enter some
ideas for medium to long term projects we can work on in the etherpad
page [1].
Thanks!,
We are gleeful to announce the release of:
cinder 8.1.0: OpenStack Block Storage
This release is part of the mitaka stable release series.
For more details, please see below.
8.1.0
^
New Features
* Support for use of 'fc_southbound_protocol' configuration setting
in the
Is this a secret ballot?
2016-08-09 17:54 GMT+08:00 xiangxinyong :
> Hello guys,
>
> Smaug is voting for the project mascot.
> Please feel free to give your vote:)
> https://etherpad.openstack.org/p/smaugmascot
>
> Thanks very much.
>
> Best Regards,
> xiangxinyong
>
>
d it here:
> https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160809
>
> See you tomorrow,
>
> On Tue, Aug 2, 2016 at 11:06 AM, Emilien Macchi <emil...@redhat.com> wrote:
>> no item in our agenda, we cancelled the meeting, see you next week!
>>
On 08/09/2016 10:22 AM, Ian Cordasco wrote:
> -Original Message-
> From: Matthew Thode
> Reply: prometheanf...@gentoo.org , OpenStack
> Development Mailing List (not for usage questions)
>
> Date:
-Original Message-
From: Matthew Thode
Reply: prometheanf...@gentoo.org , OpenStack
Development Mailing List (not for usage questions)
Date: August 9, 2016 at 09:53:53
To:
Hey Vitaly,
I solved the issue. As you pointed out,
https://github.com/openstack/sahara/blob/master/sahara/service/edp/job_manager.py#L124
was quite relevant.
However, you linked to version of this file on master branch. Liberty
branch file looks a little different:
Excerpts from Tony Breeds's message of 2016-08-09 16:38:35 +1000:
> Hi all,
> I guess this is aimed at the long term requirements team members.
>
> The current policy for approving requirements[1] bumps contains the following
> text:
>
> Changes to update the minimum version of a
Well don't let me stop ya :)
On 8/9/16, 7:21 AM, "Ian Cordasco" wrote:
>
>
>-Original Message-
>From: Steven Dake (stdake)
>Reply: OpenStack Development Mailing List (not for usage questions)
>
>Date: August
On 08/09/2016 09:25 AM, Ian Cordasco wrote:
>
>
> -Original Message-
> From: Sean Dague
> Reply: OpenStack Development Mailing List (not for usage questions)
>
> Date: August 9, 2016 at 05:44:55
> To:
1 - 100 of 136 matches
Mail list logo