And just a note that the Ops Guide session is on in the Ops track on Monday
morning:
https://www.openstack.org/summit/austin-2016/summit-schedule/events/9511
Lana
On 11/04/16 12:25, Lana Brindley wrote:
> The docs sessions are now in Sched, complete with etherpad links:
> https://www.openstack
Hi I am writing a test for exception . Following is my testing function.
@mock.patch('self.app.post_json')
def test_post_exp(self, mock_get, mock_http_error_handler):
mock_response = mock.Mock()
mock_response.raise_for_status.side_effect = db_exc.DBDuplicateEntry
mock_get.return_value
Agreed.
IMO, OpenStack is an open framework to different technologies and use cases.
Different architectures for different things make sense. Some may say that using
nova to launch docker images with hypervisor is weird, but it can be seen as
“Immutable IaaS”.
-
Interesting conversation, and I think I have more of a question than a
comment. With my understanding of OpenStack architecture, I don't
understand the point about making "Magnum dependent on Barbican".
Wouldn't this issue be completely resolved using a driver model, such as
delegating the task
Sure, so that helps, except it still has the issue of bumping up against
the mismatch of the API(s) of nova. This is why I'd rather have a
template kind of format (as say the input API) that allows for
(optionally) expressing such container specific capabilities/constraints.
Then some project
Ops are asking for you to make it easy for them to make their security weak.
And as a user of other folks clouds, i'd have no way to know the cloud is in
that mode. That seems really bad for app developers/users.
Barbican, like some of the other servises, wont become common if folks keep
trying
On Tue, Apr 12, 2016 at 8:06 PM, Adrian Otto
wrote:
> Please don't miss the point here. We are seeking a solution that allows a
> location to place a client side encrypted blob of data (A TLS cert) that
> multiple magnum-conductor processes on different hosts can reach over the
> network.
>
> We
I'd take the idea further. Imagine a typical Heat template, what you need to do
is:
- replace the VM id with Docker image id - nothing else - run the script with a
normal heat engine - the entire stack gets deployed in seconds
Done!
Well, that sounds like nova-docker. What about cinder and neutron
Hi, Lige,
What’s your email address in https://review.openstack.org? Not able to add you
as the reviewer.
Now the cross pod L2 networking BP is in review.
https://review.openstack.org/#/c/304540/, you can add yourself as reviewer and
comment on it. It’s quite important for your comments from f
Hi,
We have a very good discussion about cross OpenStack L2 networking
https://etherpad.openstack.org/p/TricircleCrossPodL2Networking and Dynamic Pod
Binding https://etherpad.openstack.org/p/TricircleDynamicPodBinding. This week
we will discuss what's missing in first release of Tricircle for
Please don't miss the point here. We are seeking a solution that allows a
location to place a client side encrypted blob of data (A TLS cert) that
multiple magnum-conductor processes on different hosts can reach over the
network.
We *already* support using Barbican for this purpose, as well as
Hi,
Reading through the thread I thought of adding following points which might
be relevant to this discussion.
1) Related to the point of providing an abstraction for deploying apps to
different form factors:
OpenStack Solum is a project which allows deploying of applications starting
from
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Tuesday, April 12, 2016 8:32 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Cc: foundat...@lists.openstack.org
> Subject: Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] On
Thanks for the hint, Masahito. A very useful command to know. It would be good
to give a hint about this in the intro to the section "3. Manual Reactive
Enforcement"
(https://github.com/openstack/congress/blob/master/doc/source/enforcement.rst).
That's where I was looking for a summary on how t
Yea that's right. Tempest will be able to run all tests(tempest one or
plugin) as long as plugin is discoverable and all services tests
interact with are reachable from Tempest installed node.
In that case, you need to configure services (keystone, congress etc)
endpoints correctly. Please refer c
Thanks for the clarification, Anusha. Sounds like I should focus my effort on
using tempest tests in Mitaka.
Thanks,
Bryan Sullivan
Date: Tue Apr 12 05:46:58 UTC 2016
From: anusha.iiitm at gmail.com
Hi Bryan,
Yes, tempest can be run outside devstack deployments. Please check the
RE
Great, glad to help.
On Tue, Apr 12, 2016 at 9:03 PM, Balázs Gibizer wrote:
> Hi,
>
> I just want to let the community know that the versioned notification
> work we started in Mitaka is planned to be continued in Newton.
> The planned goals for Newton:
> * Transform the most important notificat
I value the friendliness and approachability that contributors seek.
I am totally fine with minor mistakes in documentation.
As they make more changes, they will understand/follow the process.
+1
Regards,
Vikram Hosakote
IRC: vhosakot
From: "Steven Dake (stdake)" mailto:std...@cisco.com>>
Rep
Steve Baker wrote:
On 13/04/16 11:07, Joshua Harlow wrote:
Fox, Kevin M wrote:
I think my head just exploded. :)
That idea's similar to neutron sfc stuff, where you just say what
needs to connect to what, and it figures out the plumbing.
Ideally, it would map somehow to heat& docker COE& neut
On 04/12/2016 07:21 PM, Jay S. Bryant wrote:
> Sean,
>
> Thanks for getting the discussion started.
>
> I think R-14 might be a little tricky leading up to the 4th of July
> weekend.
>
> It seems like R-17 is coming awful quick but could be done. That or
> R-11 would be my second vote then.
R-
On 13/04/16 11:07, Joshua Harlow wrote:
Fox, Kevin M wrote:
I think my head just exploded. :)
That idea's similar to neutron sfc stuff, where you just say what
needs to connect to what, and it figures out the plumbing.
Ideally, it would map somehow to heat& docker COE& neutron sfc to
produ
Sean,
Thanks for getting the discussion started.
I think R-14 might be a little tricky leading up to the 4th of July weekend.
It seems like R-17 is coming awful quick but could be done. That or
R-11 would be my second vote then.
We have had successful meet-ups in Rochester ... yes, the gues
Hi Everyone!
Intel would be pleased to host the Nova midcycle meetup either at San
Antonio, Texas or Hillsboro, Oregon during R-15 (June 20-24) or R-11 (July
18-22) as preferred by the Nova community.
Regards
Malini
Forwarded Message
Subject:Re: [openstack-de
Fox, Kevin M wrote:
I think my head just exploded. :)
That idea's similar to neutron sfc stuff, where you just say what needs to
connect to what, and it figures out the plumbing.
Ideally, it would map somehow to heat& docker COE& neutron sfc to produce a
final set of deployment scripts and
On 12/04/16 18:16, Monika Parkar wrote:
Hi,
I am new to the openstack.
I was going through the heat usecase "heat resource-signal", I would
like to know what kind of signal we can send and how.
I have executed the below command:
# heat resource-signal stack-name resource-name
But internal work
On Tue, Apr 12, 2016 at 3:27 PM, Lance Bragstad wrote:
> Keystone's credential API pre-dates barbican. We started talking about
> having the credential API back to barbican after it was a thing. I'm not
> sure if any work has been done to move the credential API in this
> direction. From a securi
I think my head just exploded. :)
That idea's similar to neutron sfc stuff, where you just say what needs to
connect to what, and it figures out the plumbing.
Ideally, it would map somehow to heat & docker COE & neutron sfc to produce a
final set of deployment scripts and then just runs it thro
Great!
On Tue, Apr 12, 2016 at 6:24 AM, Andrew Woodward wrote:
> It's been a while since we started the puppet-ceph module on stackforge as a
> friend of OpenStack. Since then Ceph's usage in OpenStack has increased
> greatly and we have both the puppet-openstack deployment scenarios as well
> as
Hello,
I would like to step up as PTL if everybody is ok with it.
Cheers,
Ivan
- Original Message -
> From: "Martin Magr"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Cc: "Javier Pena" , "David Moreau Simard"
> , "Alan Pevec" ,
> "Ivan Chavero"
> Sent: T
On 12 April 2016 at 12:36, Anita Kuno wrote:
> On 04/12/2016 03:23 PM, Armando M. wrote:
> > On 12 April 2016 at 12:16, Matt Riedemann
> > wrote:
> >
> >>
> >>
> >> On 4/11/2016 11:56 PM, Armando M. wrote:
> >>
> >>> Hi folks,
> >>>
> >>> A provisional schedulefor the Neutron project is availabl
Fox, Kevin M wrote:
I think part of the problem is containers are mostly orthogonal to vms/bare
metal. Containers are a package for a single service. Multiple can run on a
single vm/bare metal host. Orchestration like Kubernetes comes in to turn a
pool of vm's/bare metal into a system that can
Hello everyone,
Firstly, thanks to those who were able to make it to the virtual
pre-summit sync today. The discussions went well and we already have
decent amount of feedback on most of the proposals.
Based on the discussions, feedback and other input, I've created the
tentative summit schedule
On Fri, 2016-04-08 at 16:18 +0100, Steven Hardy wrote:
> Note we're not using devtest at all anymore, the developer script
> many
> folks use is tripleo.sh:
So, I followed the flow of the gate jobs starting from jenkins builder
script, and it seems like it's using devtest (or maybe something I
co
Hi all!
We will be skipping the cross-project meeting since there are no agenda items
to discuss, but someone can add one [1] to call a meeting next time. Thanks!
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
--
Mike Perez
_
The Nova design summit sessions are now in the schedule [1].
Some of the session descriptions might need some tweaking yet, like
adding etherpad links for the specific sessions, but this is the
schedule at least.
[1]
https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?
E.1 and O.3 work for me.
Richard
Dean Troyer wrote on 04/12/2016 03:06:20 PM:
> From: Dean Troyer
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 04/12/2016 03:08 PM
> Subject: Re: [openstack-dev] [osc] Meeting time preferences for OSC team
>
> On Thu, Apr 7,
Keystone's credential API pre-dates barbican. We started talking about
having the credential API back to barbican after it was a thing. I'm not
sure if any work has been done to move the credential API in this
direction. From a security perspective, I think it would make sense for
keystone to back
On Thu, Apr 7, 2016 at 1:52 AM, Sheel Rana Insaan
wrote:
> Common votes seems for below time options
>
> E.4 - Thursday at 1600 UTC in #openstack-meeting (IRC webclient)
> O.3 - Thursday at 1900 UTC in #openstack-meeting (IRC webclient)
>
For reference, here are the proposed times again:
-
- Original Message -
> From: "Jeff Peeler"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> On Mon, Apr 11, 2016 at 3:37 AM, Steven Dake (stdake)
> wrote:
> > Hey folks,
> >
> > The reviewers in Kolla tend to nit-pick the quickstart guide to death
> > during
>
On 4/6/2016 6:15 AM, Mikhail Fedosin wrote:
Hello! Thanks for bring this topic up.
First of all, as I mentioned before, the great work was done in Mitaka,
so Glance v2 adoption in Nova it is not a question of "if", and not even
a question of "when" (in Newton), but the question of "how".
Ther
On 04/12/2016 03:37 PM, Matt Riedemann wrote:
>
>
> On 4/1/2016 8:45 AM, Sean Dague wrote:
>> The glance v2 work is currently blocked as there is no active spec,
>> would be great if someone from the glance team could get that rolling
>> again.
>>
>> I started digging back through the patches in
I think part of the problem is containers are mostly orthogonal to vms/bare
metal. Containers are a package for a single service. Multiple can run on a
single vm/bare metal host. Orchestration like Kubernetes comes in to turn a
pool of vm's/bare metal into a system that can easily run multiple c
Hi all,
In short, some Magnum team members proposed to store TLS certificates in
Keystone credential store. As Magnum PTL, I want to get agreements (or
non-disagreement) from OpenStack community in general, Keystone community in
particular, before approving the direction.
In details, Magnum le
I didn't see that mention. You mean about legacy volumes and snapshots?
On Mon, Apr 11, 2016 at 3:58 PM, Duncan Thomas
wrote:
> Ok, you're right about device naming by UUID.
>
> So we have two advantages compared to the existing system:
>
> - Keeping the same volume id (and therefore disk UUID)
On 4/1/2016 8:45 AM, Sean Dague wrote:
The glance v2 work is currently blocked as there is no active spec,
would be great if someone from the glance team could get that rolling again.
I started digging back through the patches in detail to figure out if
there are some infrastructure bits we co
On 04/12/2016 03:23 PM, Armando M. wrote:
> On 12 April 2016 at 12:16, Matt Riedemann
> wrote:
>
>>
>>
>> On 4/11/2016 11:56 PM, Armando M. wrote:
>>
>>> Hi folks,
>>>
>>> A provisional schedulefor the Neutron project is available [1]. I am
>>> still working with the session chairs and going thro
On Mon, Apr 11, 2016 at 3:37 AM, Steven Dake (stdake) wrote:
> Hey folks,
>
> The reviewers in Kolla tend to nit-pick the quickstart guide to death during
> reviews. I'd like to keep that high bar in place for the QSG, because it is
> our most important piece of documentation at present. However
On Mon, 2016-04-11 at 05:54 -0400, John Trowbridge wrote:
> Hola OOOers,
>
> It came up in the meeting last week that we could benefit from a CI
> subteam with its own meeting, since CI is taking up a lot of the main
> meeting time.
>
> I like this idea, and think we should do something similar f
On 12 April 2016 at 12:16, Matt Riedemann
wrote:
>
>
> On 4/11/2016 11:56 PM, Armando M. wrote:
>
>> Hi folks,
>>
>> A provisional schedulefor the Neutron project is available [1]. I am
>> still working with the session chairs and going through/ironing out some
>> details as well as gathering inp
Greetings,
I'm soliciting inputs, and if interested in this topic, your presence for
the upcoming BoF session on NFV Orchestration during the Austin summit,
https://www.openstack.org/summit/austin-2016/summit-schedule/events/8468
We had a packed session for a similar event in the Tokyo summit wi
Flavio Percoco wrote:
On 11/04/16 18:05 +, Amrith Kumar wrote:
Adrian, thx for your detailed mail.
Yes, I was hopeful of a silver bullet and as we’ve discussed before (I
think it
was Vancouver), there’s likely no silver bullet in this area. After that
conversation, and some further experi
On 4/11/2016 11:56 PM, Armando M. wrote:
Hi folks,
A provisional schedulefor the Neutron project is available [1]. I am
still working with the session chairs and going through/ironing out some
details as well as gathering input from [2].
I hope I can get something more final by the end of thi
Hello,
Separate job for testing live-migration with different storage
configurations(No shared storage/NFS/Ceph was implemented during Mitaka and
available to be executed using experimental pipeline.
The job is ready but shows same stability as
gate-tempest-dsvm-multinode-full.
Bugs like [1] [2]
On 12 April 2016 at 07:08, Michael Johnson wrote:
> Armando,
>
> Is there any way we can move the "Neutron: Development track: future
> of *-aas projects" session? I overlaps with the LBaaS talk:
>
> https://www.openstack.org/summit/austin-2016/summit-schedule/events/6893?goback=1
>
> Michael
>
I'm definitely glad we got puppet-ceph to where it is today and I have
complete trust in the Puppet-OpenStack team to take it to the next
level.
With that announcement, I have to do one of my own -- I am stepping
down as a puppet-ceph core.
My day-to-day work does not involve Ceph anymore and as
On 12/04/2016 18:39, Jeremy Stanley wrote:
> On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote:
>> If a team has already done a TA (e.g. as part of an internal
>> product TA) (and produced all the documentation) would this meet
>> the requirements?
>>
>> I ask, as Designate looks like it me
On 2016-04-05 00:45:20 -0400 (-0400), Jay Pipes wrote:
> The proposal is to have the hardware companies donate hardware and
> sysadmins to setup and maintain a *single* third-party CI lab
> environment running the *upstream infra CI toolset* in one
> datacenter at first, moving to multiple datacent
On 12/04/2016 18:37, "Jeremy Stanley" wrote:
>On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote:
>> If a team has already done a TA (e.g. as part of an internal
>> product TA) (and produced all the documentation) would this meet
>> the requirements?
>>
>> I ask, as Designate looks like
On 2016-04-02 14:40:57 + (+), Steven Dake (stdake) wrote:
[...]
> IANAL and writing these things correctly is hard to do properly );
> involving the community around the pain points of the tagging
> process is what I'm after.
[...]
Nobody on the VMT is a lawyer either, and when I wrote the
On 4/12/16, 10:37 AM, "Jeremy Stanley" wrote:
>On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote:
>> If a team has already done a TA (e.g. as part of an internal
>> product TA) (and produced all the documentation) would this meet
>> the requirements?
>>
>> I ask, as Designate looks lik
Hi Folks - I'm looking into the options for Intel to host in Hillsboro Oregon.
Stay tuned for more details.
Thanks
Carol
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
Sent: Tuesday, April 12, 2016 9:05 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [o
On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote:
> If a team has already done a TA (e.g. as part of an internal
> product TA) (and produced all the documentation) would this meet
> the requirements?
>
> I ask, as Designate looks like it meets nearly all the current
> requirements - the
On 04/12/2016 01:05 PM, Anita Kuno wrote:
> On 04/12/2016 12:45 PM, Matt Riedemann wrote:
>> I've stubbed out the newton design summit etherpad wiki so people can
>> start populating this now.
>>
>> https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads
>>
> Keep in mind we still haven't fu
On 2016-03-31 15:15:23 -0400 (-0400), michael mccune wrote:
[...]
> * what is the process for performing an analysis
>
> * how will an analysis be formally recognized and approved
>
> * who will be doing these analyses
I intentionally didn't specify when writing the
vulnerability:managed tag des
> On Apr 12, 2016, at 1:12 PM, Steve Gordon wrote:
>
>
>
> - Original Message -
>> From: "Calum Loudon"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>> ,
>> "openstack-operators"
>> Sent: Wednesday, April 6, 2016 6:09:16 AM
>> Subject: Re: [openstack-dev] T
Hi all,
We discussed this in our last team meeting, and we were in disagreement. Some
of us preferred option #1, others preferred option #2. I would suggest to leave
this topic to the design summit so that our team members would have more times
to research each option. If we are in disagreement
- Original Message -
> From: "Calum Loudon"
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> "openstack-operators"
> Sent: Wednesday, April 6, 2016 6:09:16 AM
> Subject: Re: [openstack-dev] Telco Working Group meeting for Wednesday April
> 6th CANCELLED
>
>
Hi,
We are nerdy to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 04.04.2016):
- Ironic: 200 bugs (+4) + 163 wishlist items. 25 new, 136 in progress (+1),
0 critical,
On 04/12/2016 12:45 PM, Matt Riedemann wrote:
> I've stubbed out the newton design summit etherpad wiki so people can
> start populating this now.
>
> https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads
>
Keep in mind we still haven't fully addressed all the consequences of
the wiki sp
I've stubbed out the newton design summit etherpad wiki so people can
start populating this now.
https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads
--
Thanks,
Matt Riedemann
__
OpenStack Development Mailing
Hello,
It's nova-compute service which is configuring it. This service is running on
compute node: http://docs.openstack.org/developer/nova/architecture.html
--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl
Dnia wtorek, 12 kwietnia 2016 16:16:25 CEST 张晨 pisze:
> Thx for the an
I'm definitely guilty of nit picking docs. I'm fine with holding back and
following up with a patch to fix any grammar/misspelling mistakes. +1
-Ryan
- Original Message -
From: "Paul Bourke"
To: openstack-dev@lists.openstack.org
Sent: Tuesday, April 12, 2016 4:49:09 AM
Subject: Re: [
On 4/11/2016 5:54 PM, Michael Still wrote:
On Tue, Apr 12, 2016 at 6:49 AM, Matt Riedemann
mailto:mrie...@linux.vnet.ibm.com>> wrote:
A few people have been asking about planning for the nova midcycle
for newton. Looking at the schedule [1] I'm thinking weeks R-15 or
R-11 work the
Thank you Morgan for quick fixes proposed!
On Tue, Apr 12, 2016 at 6:19 PM, Morgan Fainberg
wrote:
> Sorry Missed the copy/paste of links:
>
> https://bugs.launchpad.net/keystone/+bug/1567403 [0]
> https://bugs.launchpad.net/keystone/+bug/1567413 [1]
>
> [0]
> https://review.openstack.org/#/q/I4
Flavio, and whom'ever else who's available to attend,
We have a summit session for instance users listed here that could be part of
the solution:
https://www.openstack.org/summit/austin-2016/summit-schedule/events/9485
Please attend if you can.
--
+1 for a basic common abstraction.
Yes, I think it would be good to have a summit session on that. However,
before the session, it would really be helpful if the folks with proposals
got together and/or reviewed each other's proposals, and summarized their
findings. You may find after reviewing the proposals, that eg only 2 are
real
Have a look at this script:
https://review.openstack.org/#/c/158003/1/bin/neutron-local-port
Nova does basically the same thing but plugs it into the vm.
Thanks,
Kevin
From: 张晨 [zhangchen9...@126.com]
Sent: Tuesday, April 12, 2016 1:16 AM
To: OpenStack Developmen
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160412
>
> We'll also have open discussion for bugs & reviews, so anyone is welcome
> to join.
We did our meeting, notes are available here:
http://eavesdrop.openstack.org/meetings/puppet_openstack/2016/puppet_op
HP facility just outside Dublin (ireland) is available again, depending on
dates
On 12 April 2016 at 17:05, Sean McGinnis wrote:
> Hey Cinder team (and those interested),
>
> We've had a few informal conversations on the channel and in meetings,
> but wanted to capture some things here and sprea
Sorry Missed the copy/paste of links:
https://bugs.launchpad.net/keystone/+bug/1567403 [0]
https://bugs.launchpad.net/keystone/+bug/1567413 [1]
[0]
https://review.openstack.org/#/q/I4857cfe1e62d54c3c89a0206ffc895c4cf681ce5,n,z
[1] https://review.openstack.org/#/c/304688/
--Morgan
On Tue, Apr 12
Fixes have been proposed for both of these bugs.
Cheers,
--Morgan
On Tue, Apr 12, 2016 at 12:38 AM, Dina Belova wrote:
> Matt,
>
> Thanks for sharing the information about your benchmark. Indeed we need to
> follow up on this topic (I'll attend the summit). Let's try to collect as
> much inform
On 04/12/2016 10:05 AM, Sean McGinnis wrote:
> Hey Cinder team (and those interested),
>
> We've had a few informal conversations on the channel and in meetings,
> but wanted to capture some things here and spread awareness.
>
> I think it would be good to start planning for our Newton midcycle.
And I'll add Raleigh NC NetApp is available too. Nothing better than summer in
the South :)
-Original Message-
From: D'Angelo, Scott [mailto:scott.dang...@hpe.com]
Sent: Tuesday, April 12, 2016 10:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [ope
As a note, there will be a design session around the API refactor
efforts going on. Microversioning will be a topic.
On Tue, 2016-04-12 at 14:59 +0200, Ihar Hrachyshka wrote:
> Xianshan wrote:
>
> > Hi, Duncan & michael,
> > Thanks a lot for your replies.
> >
> > Definitely I agree with you tha
On 04/11/2016 09:45 PM, Tony Breeds wrote:
> On Mon, Apr 11, 2016 at 03:49:16PM -0500, Matt Riedemann wrote:
>> A few people have been asking about planning for the nova midcycle for
>> newton. Looking at the schedule [1] I'm thinking weeks R-15 or R-11 work the
>> best. R-14 is close to the US Jul
The RDO community is pleased to announce the general availability of the
RDO build for OpenStack Mitaka for RPM-based distributions - CentOS
Linux 7 and Red Hat Enterprise Linux. RDO is suitable for building
private, public, and hybrid clouds and Mitaka is the 13th release from
the OpenStack projec
I'll throw this out there: Fort Collins HPE site is available.
Scott D'Angelo (scottda)
From: Sean McGinnis [sean.mcgin...@gmx.com]
Sent: Tuesday, April 12, 2016 8:05 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Cinder] Newton Midcycle
On 11/04/16 18:05 +, Amrith Kumar wrote:
Adrian, thx for your detailed mail.
Yes, I was hopeful of a silver bullet and as we’ve discussed before (I think it
was Vancouver), there’s likely no silver bullet in this area. After that
conversation, and some further experimentation, I found that
Hi Nikhil,
2016-04-12 5:59 GMT+03:00 Nikhil Komawar :
> Hello,
>
> I was hoping to make some changes to the stackalytics dashboard
> specifically of this type [1] following my requested suggestions here
> [2]; possibly add a few extra columns for +0s and just Bot +1s. I think
> having this info g
On 11/04/16 16:53 +, Adrian Otto wrote:
Amrith,
I respect your point of view, and agree that the idea of a common compute API
is attractive… until you think a bit deeper about what that would mean. We
seriously considered a “global” compute API at the time we were first
contemplating Magnum.
This discussion needs to be happening on openstack-dev too, so
cc'ing that list in as well. The top of the thread is at
http://lists.openstack.org/pipermail/openstack/2016-April/015864.html
On Tue, 12 Apr 2016, Chris Dent wrote:
On Tue, 12 Apr 2016, Nadya Shakhat wrote:
I'd like to discus
On Thu, Apr 07, 2016 at 02:42:09AM +, Jeremy Stanley wrote:
> On 2016-04-06 18:33:06 +0300 (+0300), Igor Belikov wrote:
> [...]
> > I suppose there are security issues when we talk about running
> > custom code on bare metal slaves, but I'm not sure I understand
> > the difference from running
Armando,
Is there any way we can move the "Neutron: Development track: future
of *-aas projects" session? I overlaps with the LBaaS talk:
https://www.openstack.org/summit/austin-2016/summit-schedule/events/6893?goback=1
Michael
On Mon, Apr 11, 2016 at 9:56 PM, Armando M. wrote:
> Hi folks,
>
Hey Cinder team (and those interested),
We've had a few informal conversations on the channel and in meetings,
but wanted to capture some things here and spread awareness.
I think it would be good to start planning for our Newton midcycle.
These have been incredibly productive in the past (at lea
On 2016-04-12 08:31, Andreas Jaeger wrote:
> On 2016-04-12 03:33, Nikhil Komawar wrote:
>> To close this:
>>
>> This has been fixed as a part of the earlier opened bug
>> https://bugs.launchpad.net/glance-store/+bug/1568767 and other is
>> duplicated.
>>
>
> Yes, it's fixed now.
And you have rele
We are satisfied to announce the release of:
pbr 1.9.0: Python Build Reasonableness
With source available at:
http://git.openstack.org/cgit/openstack-dev/pbr
Please report issues through launchpad:
http://bugs.launchpad.net/pbr
For more details, please see below.
Changes in pbr 1.8.1
On Tue, Apr 5, 2016, at 09:57 AM, Ryan McNair wrote:
> >It is believed that reservation help to to reserve a set of resources
> >beforehand and hence eventually preventing any other upcoming request
> >(serial or parallel) to exceed quota if because of original request the
> >project might have r
On Thu, Apr 07, 2016 at 06:36:20AM -0400, Sean Dague wrote:
> On 04/07/2016 03:26 AM, Juvonen, Tomi (Nokia - FI/Espoo) wrote:
> > Hi Nova, Ops, stackers,
> >
> > I am trying to figure out different use cases and requirements there
> > would be for host maintenance and would like to get feedback a
We are content to announce the release of:
doc8 0.7.0: Style checker for Sphinx (or other) RST documentation
For more details, please see below.
Changes in doc8 0.6.0..0.7.0
a96c31f Skip long line check for rst definition list term
f6cb930 Remove argparse from requi
We are tickled pink to announce the release of:
glance_store 0.13.1: OpenStack Image Service Store Library
This release is part of the mitaka stable release series.
With source available at:
http://git.openstack.org/cgit/openstack/glance_store
With package available at:
https://pypi.p
1 - 100 of 139 matches
Mail list logo
