Vladimir,
I think this call is too late to change a structure for now. I suggest that
we always respect the policy we've accepted, and follow it.
If Component Leads role is under a question, then I'd continue the
discussion, hear opinion of current component leads, and give this a time
to be discu
Hi,
I'm writing a tempest scenario test, the test will check the SCTP protocol,
the ncat utility in the current image of cirros does not support the "--sctp"
flag,
so we opened a bug : https://bugs.launchpad.net/cirros/+bug/1540359
Is there any change I'll get a commit on my code while using ano
Hi Team,
Anyone please help on writing a custom meters in open-stack kilo
version.
I tried going through many docs, but i couldn't find out any hint.
please guide me how to customize it as per new parameters.
Thanks in Advance [😊] [😊] [😊] [😊]
[😊]
Thanks
Monty Taylor wrote:
On 03/28/2016 06:09 PM, joehuang wrote:
One question about this ' The transition to the "big tent" governance
model is now finished, with all the expected projects now officially
part of the OpenStack community. The big tent is all about community:
answering the "are you one
Hi,
On Tue, Mar 29, 2016 at 9:17 AM, Eyal Dannon wrote:
> Hi,
>
> I'm writing a tempest scenario test, the test will check the SCTP protocol,
> the ncat utility in the current image of cirros does not support the
> "--sctp" flag,
> so we opened a bug : https://bugs.launchpad.net/cirros/+bug/1540
> -Original Message-
> From: Jay Pipes [mailto:[email protected]]
> Sent: Friday, March 25, 2016 10:20 PM
> To: [email protected]
> Subject: Re: [openstack-dev] [nova] The same SRIOV / NFV CI failures missed a
> regression, why?
>
> On 03/24/2016 09:35 AM, Matt Riedemann
Matt Riedemann wrote:
I see one problem. The single stable team fishbowl session is scheduled
for the last slot on Thursday (5pm). The conflict I have with that is
the nova team does it's priority/scheduling talk in the last session on
the last day for design summit fishbowl sessions (non-meetup
On Tue, Mar 29, 2016 at 9:46 AM, Eran Kuris wrote:
>
>
> - Original Message -
> > From: "Jordan Pittier"
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> [email protected]>
> > Cc: "Eran Kuris"
> > Sent: Tuesday, March 29, 2016 10:34:55 AM
> > S
The discussion around Bug 1550250 [1] doesn't show a clear path on how
to proceed. In short, it's about if we want to keep the flag
"delete_on_termination" for volumes which get migrated. Right now that
flag gets reset during the migration process. The patch [2] is stalled
by the missing decision.
Hi, all,
I follow the advice given by Zhiyuan, and it works. For the port error,
somebody removes the line "iniset $NOVA_CONF DEFAULT network_api_class
nova.network.neutronv2.api.API" in lib/neutron-legacy. For the unknown
auth_plugin error in the first mail, somebody changes the auth_plugin to
au
Le 29/03/2016 09:48, Thierry Carrez a écrit :
Matt Riedemann wrote:
I see one problem. The single stable team fishbowl session is scheduled
for the last slot on Thursday (5pm). The conflict I have with that is
the nova team does it's priority/scheduling talk in the last session on
the last day
Hi,
We are using the official Fedora Atomic 23 images here (on Mitaka M1
however) and it seems to work fine with at least Kubernetes and Docker
Swarm.
Any reason to continue building specific Magnum image ?
Regards,
Mathieu
Le mercredi 23 mars 2016 à 12:09 +0100, Yolanda Robla Mota a écrit :
>
On 03/29/2016 09:14 AM, Markus Zoeller wrote:
> The discussion around Bug 1550250 [1] doesn't show a clear path on how
> to proceed. In short, it's about if we want to keep the flag
> "delete_on_termination" for volumes which get migrated. Right now that
> flag gets reset during the migration proce
On 03/23/2016 04:06 PM, Mike Perez wrote:
> Hey all,
>
> I've been talking to a variety of projects about lack of install guides. This
> came from me not having a great experience with trying out projects in the big
> tent.
>
> [...]
Sorry to jump in this conversation a bit later, as I missed th
Hi Yipei,
Glad to hear that you can successfully boot VMs. So the problems are caused
by the incompatibility of the nova, neutron and devstack code trees in your
environment. Yeah, what you did is what I always do. When devstack fails to
start or has some troubles, find the reason then modify the
Hi
The idea is to build own images using diskimage-builder, rather than
downloading the image from external sources. By that way, the image can
live in our mirrors, and is built using the same pattern as other images
used in OpenStack.
It also opens the door to customize the images, using custo
> From: Augustina Ragwitz
> To:
> Date: 03/25/2016 08:52 PM
> Subject: [openstack-dev] [nova] Bug for image_cache_manager refactoring
>
> I came across a bug filed back in August [1] that brought up a
> potential issue with the image_cache_manager in that the loop for
> building the BlockDevic
Greetings,
Please, be informed that the source code of Nailgun API extension has
landed to the designated repository [1]. Project was code named
'tuning-box'. We are working to integrate it into the build and testing
systems provided by Fuel infra. I suggest that the FFE can be closed.
I'd like t
Dear colleagues,
This is a part of our plan to make Fuel even more modular.
Governance patch: https://review.openstack.org/#/c/298603/
Project-config patch: https://review.openstack.org/#/c/298615/
Launchpad project: https://launchpad.net/shotgun
Wiki page: https://wiki.openstack.org/wiki/Shotgun
2016-03-29 16:28 GMT+08:00 Nikola Đipanov :
> On 03/29/2016 09:14 AM, Markus Zoeller wrote:
> > The discussion around Bug 1550250 [1] doesn't show a clear path on how
> > to proceed. In short, it's about if we want to keep the flag
> > "delete_on_termination" for volumes which get migrated. Right
Oleg and team,
Thanks very much for your efforts to make this happened. I'm sure this
experience will help us to implement thorough "Day 2" maintenance flow in
future Fuel releases.
Vladimir Kozhukalov
On Tue, Mar 29, 2016 at 12:06 PM, Oleg Gelbukh
wrote:
> Greetings,
>
> Please, be informed
On 29/03/16 09:38, Thomas Goirand wrote:
> On 03/23/2016 04:06 PM, Mike Perez wrote:
>> Hey all,
>>
>> I've been talking to a variety of projects about lack of install guides. This
>> came from me not having a great experience with trying out projects in the
>> big
>> tent.
>>
>> [...]
>
> Sorry t
Hello All,
I have been working on OpenStack for the past year, currently the PTL of two
projects part of the big-tent: Dragonflow and Kuryr and contributing to OVN and
to Neutron core.
The past year is by no doubt the best year of my career, working with
the community
and doing so openly for 100%
The live migration meeting is today at usual time, but beware: a lot of time
zones have switch to summer time this week.
Agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration
Paul
P.S. Sorry for late update - it was a national holiday in UK yesterday
___
Hi Saltstackers,
A kind reminder for this week's #openstack-salt meeting. This meeting and
future meetings will be held at our new time, 1300UTC. Also, the IRC channel
has been updated to #openstack-meeting-4. More on the agenda [1].
[1]. https://wiki.openstack.org/wiki/Meetings/openstack-sal
Hello,
A few weeks ago I made a [blog posting][1] in which I wrote about the
issues I would consider important to address if I were a member of the
Technical Committee. Several people encouraged me to act on my concerns
and actually run.
[1]: https://anticdent.org/if-i-were-on-the-openstack-tc.
(This was also proposed in our elections repo:
https://review.openstack.org/298676)
I'm announcing my candidacy for a position on the OpenStack Tecnical Committee.
I had the honor to have been elected last year for a position on the TC and it'd
be an honor for me to be re-elected for one more p
On 03/29/2016 11:56 AM, Neil Jerram wrote:
> On 29/03/16 09:38, Thomas Goirand wrote:
>> On 03/23/2016 04:06 PM, Mike Perez wrote:
>>> Hey all,
>>>
>>> I've been talking to a variety of projects about lack of install guides.
>>> This
>>> came from me not having a great experience with trying out p
On 29/03/16 12:40, Thomas Goirand wrote:
>
> The documentation people decided to *not* publish the Debian
> install-guide (and remove the link to it) even though it can be
> generated and (to my opinion, which is probably biased) works well.
>
> I'd like to know the steps needed to restore a workin
Some additional links to what this sort of looks like right now -
http://docs-draft.openstack.org/71/298671/1/check/gate-nova-docs/c9e7f66//doc/build/html/rest_api/
Which is built off an RST file that looks like - http://tinyurl.com/hjqpjdm
The notable additions are the ".. rest_method::" stanza,
Mike,
Inline comments.
Vladimir,
> I think this call is too late to change a structure for now. I suggest
> that we always respect the policy we've accepted, and follow it.
>
> If Component Leads role is under a question, then I'd continue the
> discussion, hear opinion of current component leads
Dear all,
Fuel currently supports deployment of OpenStack using DEB packages
(particularly Ubuntu, and Debian in near future). But we also used to
deploy OpenStack on CentOS, but at some point we switched our focus on
Ubuntu. It is not so hard to implement deployment of RDO using Fuel.
Volunteers
Due to release-critical issues spotted in Ceilometer during RC1 testing,
a new release candidate was created for Mitaka. You can find the RC2
source code tarballs at:
https://tarballs.openstack.org/ceilometer/ceilometer-6.0.0.0rc2.tar.gz
Unless new release-critical issues are found that warran
Hi Jay, Matt, Levi et al,
The Intel NFV CI problems were fixed last week.
Also, I think if the CIs would have voting right it would attract more
attention.
I'd be happy to work with OpenStack Infra team on getting our NFV CI the voting
level/rights. To do it right, though, it'd be great to have
Due to release-critical issues spotted in Cinder during RC1 testing, a
new release candidate was created for Mitaka. You can find the RC2
source code tarballs at:
https://tarballs.openstack.org/cinder/cinder-8.0.0.0rc2.tar.gz
Unless new release-critical issues are found that warrant a last-min
Hi Thierry,
If a new tarball will necessary, is it possible to get this included, too?
https://review.openstack.org/#/c/272437/
Seems this is not critical enough, but a straight fix.
Br,
Gyorgy
-Original Message-
From: Thierry Carrez [mailto:[email protected]]
Sent: 29 March 2016 3
Hi,
We have weekly Nova API meeting tomorrow. 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
Hello,
I am using Ironic for deploying baremetal to my openstack environment.
Using Liberty version on Ubuntu 14.04. I followed Ironic documentation to
deploy x86 servers using pxe_ipmitool. Now I have a working Ironic setup
for PXE boot. I also want to add my test board running ARM 64 bit CPU to
That patch is now approved and in the process of merging; once it is
merged, you can propose a backport - if it doesn't make the release, it
will at least be one the stable tree.
On 29 March 2016 at 16:18, Gyorgy Szombathelyi <
[email protected]> wrote:
> Hi Thierry,
>
> If a
Hi!
Once Shotgun is pulled out of Fuel, may I suggest renaming it to
something different? I know in the past that Anita and a few others
thought the name was not something we should really be encouraging in
the OpenStack ecosystem.
Just something to consider since it's being decoupled anyway
Greetings!
I am announcing my candidacy for the OpenStack Technical Committee. As a
long-time developer, I have been part of projects that have succeeded and
others that have not; in either event, I always learned something to apply to
the next endeavor. I would like to use that experience to h
Curtis,
Please take a look at https://review.openstack.org/#/c/298765/ as its
probably a good place to start digging into OVS.
Travis Truman
IRC: automagically
On 3/24/16, 12:37 PM, "Curtis" wrote:
>OK thanks everyone. I will put on my learnening hat and start digging
>into this.
>
>Thanks,
>C
On Tue, Mar 29, 2016 at 04:59:09PM +0300, Senthilprabu Shanmugavel wrote:
> Hello,
>
> I am using Ironic for deploying baremetal to my openstack environment.
> Using Liberty version on Ubuntu 14.04. I followed Ironic documentation to
> deploy x86 servers using pxe_ipmitool. Now I have a working I
On 03/29/2016 08:56 AM, Znoinski, Waldemar wrote:
> Hi Jay, Matt, Levi et al,
>
> The Intel NFV CI problems were fixed last week.
> Also, I think if the CIs would have voting right it would attract more
> attention.
>
> I'd be happy to work with OpenStack Infra team on getting our NFV CI the
>
On 29/03/16 15:17, Jay Pipes wrote:
> Hi!
>
> Once Shotgun is pulled out of Fuel, may I suggest renaming it to
> something different? I know in the past that Anita and a few others
> thought the name was not something we should really be encouraging in
> the OpenStack ecosystem.
>
> Just something
Hi,
We are lucky 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 14.03.2016):
- Ironic: 179 bugs (+12) + 164 wishlist items (-10). 25 new (+6), 124 in
progress (+3),
Hi,
We temporary cancel the nova notification subteam meeting due to low
participation and low amount of thing to discuss. We will resurrect it after
the summit.
The way forward with the notification transformation is under review [1] so we
can discuss the issues there or you can ping me (gi
Hi Everyone:
As Mitaka branch was cut yesterday, I would like to request a backport
exception to get gnocchi patches[1][2][3] into stable/mitaka. It
should low risk feature as we decided not to set ceilometer to use
gnocchi by default. So ceilometer would work as is and gnocchi is
deployed along s
Nova has had some long-standing bugs that Sahid is trying to fix here [1].
You can create a network in neutron with port_security_enabled=False.
However, the bug is that since Nova adds the 'default' security group to
the request (if none are specified) when allocating networks, neutron
raises
Great, thanks!
From: Duncan Thomas [mailto:[email protected]]
Sent: 29 March 2016 4:01 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: [email protected]
Subject: Re: [openstack-dev] [Cinder] Mitaka RC2 available
That patch is now approved and in the pro
Should we propose options and then arrange a poll?
> 29 бер. 2016 р. о 16:40 Neil Jerram написав(ла):
>
> On 29/03/16 15:17, Jay Pipes wrote:
>> Hi!
>>
>> Once Shotgun is pulled out of Fuel, may I suggest renaming it to
>> something different? I know in the past that Anita and a few others
>> t
Thanks Jim. WA did the trick. Very well explained.
Should I raise a bug for fake driver's power state?.
On Tue, Mar 29, 2016 at 5:30 PM, Jim Rollenhagen
wrote:
> On Tue, Mar 29, 2016 at 04:59:09PM +0300, Senthilprabu Shanmugavel wrote:
> > Hello,
> >
> > I am using Ironic for deploying baremeta
Due to release-critical issues spotted in Heat during RC1 testing, a new
release candidate was created for Mitaka. You can find the RC2 source
code tarball at:
https://tarballs.openstack.org/heat/heat-6.0.0.0rc2.tar.gz
Unless new release-critical issues are found that warrant a last-minute
re
n
> #openstack-meeting4.
>
> https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack
>
> As usual, free free to bring topics in this etherpad:
> https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160329
>
> We'll also have open discussion for bugs & reviews,
On Mon, Mar 28, 2016 at 7:25 PM, Wang, Yalei wrote:
> Someone is working on full distributed SNAT, like this:
>
> https://www.openstack.org/summit/tokyo-2015/videos/presentation/network-node-is-not-needed-anymore-completed-distributed-virtual-router
>
> From: Zhi Chang [mailto:chang...@unitedstack
Hey folks,
Consider this proposal a +1 in favor of Vikram joining the core reviewer team.
His reviews are outstanding. If he doesn't have anything useful to add to a
review, he doesn't pile on the review with more -1s which are slightly
disheartening to people. Vikram has started a trend amo
+1
On 29/03/16 17:07, Steven Dake (stdake) wrote:
Hey folks,
Consider this proposal a +1 in favor of Vikram joining the core reviewer
team. His reviews are outstanding. If he doesn’t have anything useful
to add to a review, he doesn't pile on the review with more –1s which
are slightly dishea
Dear colleagues,
I have prepared a document [1] that describes some aspects
of possible testing pipeline in a component based
development environment. The main idea of the proposed
pipeline is to untie two steps:
1) Merge the code to git
2) Adopt changes to Fuel
By that I mean Fuel should be an
On 03/29/2016 08:41 AM, Roman Prykhodchenko wrote:
Should we propose options and then arrange a poll?
Yup, ++ :)
29 бер. 2016 р. о 16:40 Neil Jerram написав(ла):
On 29/03/16 15:17, Jay Pipes wrote:
Hi!
Once Shotgun is pulled out of Fuel, may I suggest renaming it to
something different? I
On Tue, Mar 29, 2016 at 11:05:00AM -0400, Pradeep Kilambi wrote:
> Hi Everyone:
>
> As Mitaka branch was cut yesterday, I would like to request a backport
> exception to get gnocchi patches[1][2][3] into stable/mitaka. It
> should low risk feature as we decided not to set ceilometer to use
> gnocc
Absolutely fantastic. Great job Emilien and the Puppet-Openstack team.
We've made great progress cycle over cycle, and now have closed our release
before most of the projects we support.
On Mon, Mar 28, 2016 at 3:55 PM Emilien Macchi wrote:
> Puppet OpenStack team has the immense pleasure to ann
+1
- Original Message -
From: "Paul Bourke"
To: [email protected]
Sent: Tuesday, March 29, 2016 12:10:38 PM
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core
Reviewer
+1
On 29/03/16 17:07, Steven Dake (stdake) wrote:
> Hey folks,
>
> Consider
During the Mitaka cycle, the release team worked on automation for
tagging and documenting releases [1]. For the first phase, we focused
on official teams with the release:managed tag for their deliverables,
to keep the number of projects manageable as we built out the tools
and processes we needed
Please, propose your options here then:
https://etherpad.openstack.org/p/shotgun-rename
> 29 бер. 2016 р. о 18:15 Jay Pipes написав(ла):
>
> On 03/29/2016 08:41 AM, Roman Prykhodchenko wrote:
>> Should we propose options and then arrange a poll?
>
> Yup, ++ :)
>
>>> 29 бер. 2016 р. о 16:40 Ne
On Mon, Mar 28, 2016 at 06:53:25PM -0400, Emilien Macchi wrote:
> Puppet OpenStack team has the immense pleasure to announce the release
> of 24 Puppet modules.
>
> Some highlights and major features:
>
> Keystone:
> * Federation with Mellon support
> * Support for multiple LDAP backends
> * Usag
Thanks Markus (and Hans)!
---
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ.
We are eager to announce the release of:
django_openstack_auth 2.2.1: Django authentication backend for use
with OpenStack Identity
This release is part of the mitaka stable release series.
With source available at:
http://git.openstack.org/cgit/openstack/django_openstack_auth/
With packag
On Tue, Mar 29, 2016 at 8:13 AM, Truman, Travis
wrote:
> Curtis,
>
> Please take a look at https://review.openstack.org/#/c/298765/ as its
> probably a good place to start digging into OVS.
>
Perfect, thanks, am looking into it now. :)
Thanks,
Curtis.
> Travis Truman
> IRC: automagically
>
> On
Fellow Kolla developers,
If you plan to be in Austin on Monday of OpenStack Summit week, there is a
fantastic opportunity for us to receive feedback from Operators that Carol
Barrett pointed out to me. The official Operator summit schedule is yet to be
defined.
The Operator summit planning Et
On Mon, Mar 21, 2016 at 12:26 PM, Russell Bryant wrote:
> On Thu, Mar 17, 2016 at 1:45 AM, Hong Hui Xiao
> wrote:
>
>> Hi Russell.
>>
>> Since the "ovn-bridge-mapping" will become accessible in OVN Southbound
>> DB, do you meant that neutron plugin can read those bridge mappings from
>> the OVN
Yolanda,
That is a fantastic objective. Matthieu asked why build our own images if
the upstream images work and need no further customization?
Regards
-steve
On 3/29/16, 1:57 AM, "Yolanda Robla Mota"
wrote:
>Hi
>The idea is to build own images using diskimage-builder, rather than
>downloading
We are psyched to announce the release of:
python-barbicanclient 4.0.1: Client Library for OpenStack Barbican Key
Management API
This release is part of the mitaka stable release series.
With source available at:
https://git.openstack.org/cgit/openstack/python-barbicanclient/
Please report
Steve,
I’m very interested in having an image locally cached in glance in each of the
clouds used by OpenStack infra. The local caching of the glance images will
produce much faster gate testing times. I don’t care about how the images are
built, but we really do care about the performance outc
I've been playing with this a bit on this patch set [1]. I haven't
gotten very far yet but it has me thinking.
Calico has a similar use case in mind as I do. Essentially, we both
want to group subnets to allow for aggregation of routes. (a) In
routed networks, we want to group them by segment a
Excerpts from Thomas Goirand's message of 2016-03-29 13:37:14 +0200:
> On 03/29/2016 11:56 AM, Neil Jerram wrote:
> > On 29/03/16 09:38, Thomas Goirand wrote:
> >> On 03/23/2016 04:06 PM, Mike Perez wrote:
> >>> Hey all,
> >>>
> >>> I've been talking to a variety of projects about lack of install g
> On Mar 29, 2016, at 08:39, Senthilprabu Shanmugavel
> wrote:
>
> Thanks Jim. WA did the trick. Very well explained.
>
> Should I raise a bug for fake driver's power state?.
That would be great, thanks in advance! :)
// jim
>
>> On Tue, Mar 29, 2016 at 5:30 PM, Jim Rollenhagen
>> wro
I just discovered a bug that¹s probably been around a long time but hidden
by exception suppression. https://bugs.launchpad.net/congress/+bug/1563495
When an auth attempt fails due to token expiry, Congress Glance driver
obtains a new token from keystone and sets it in Glance client, but for
some r
Awesome.
> Neutron:
> > * Support of LBaaSv2
> > * More SDN integrations: OpenDayLight, PlugGrid, Midonet
> > * Use modern parameters for Nova notifications
>
Just a minor correction, the SDN vendor is PLUMgrid here.
--
Regards,
Qasim Sarfraz
_
At the Mitaka Summit we had a double session on the Service Catalog,
where we stood, and where we could move forward. Even though the service
catalog isn't used nearly as much as we'd like, it's used in just enough
odd places that every change pulls on a few other threads that are
unexpected. So th
Hi jay,
There was no ability to setup this configuration WITH Neutron SR-IOV ML2 agent
in Liberty. That what you pointed out and you’re totally correct.
But in Liberty, you’re not required to use Neutron SR-IOV ML2 agent to get this
functionality works. And if you configure only nova-compute an
On Tue, Mar 29, 2016 at 3:14 PM, Qasim Sarfraz wrote:
> Awesome.
>
>> > Neutron:
>> > * Support of LBaaSv2
>> > * More SDN integrations: OpenDayLight, PlugGrid, Midonet
>> > * Use modern parameters for Nova notifications
>
> Just a minor correction, the SDN vendor is PLUMgrid here.
Sorry for that
Hi,
I am writing a patchset to build a mapping between hosts and network
segments. The goal of this mapping is to be able to say whether a host has
access to a given network segment. I am building this mapping assuming that
if a host A has a bridges mapping containing 'physnet 1' and a segment has
On Wed, Mar 30, 2016 at 12:32 AM, Emilien Macchi wrote:
> On Tue, Mar 29, 2016 at 3:14 PM, Qasim Sarfraz
> wrote:
> > Awesome.
> >
> >> > Neutron:
> >> > * Support of LBaaSv2
> >> > * More SDN integrations: OpenDayLight, PlugGrid, Midonet
> >> > * Use modern parameters for Nova notifications
> >
Congratulations to everyone involved :D
2016-03-29 16:32 GMT-03:00 Emilien Macchi :
> On Tue, Mar 29, 2016 at 3:14 PM, Qasim Sarfraz
> wrote:
> > Awesome.
> >
> >> > Neutron:
> >> > * Support of LBaaSv2
> >> > * More SDN integrations: OpenDayLight, PlugGrid, Midonet
> >> > * Use modern parameter
Some TripleO folks are currently working hard on making automation for
upgrading TripleO between major OpenStack releases.
One of the biggest challenges is how to deal with Puppet who usually
notify Services when configuration change and Pacemaker who actually
manage the services.
Currently, we do
Thanks for bringing this up Eric!
On 3/29/16 4:01 PM, Eric K wrote:
> I just discovered a bug that¹s probably been around a long time but hidden
> by exception suppression. https://bugs.launchpad.net/congress/+bug/1563495
> When an auth attempt fails due to token expiry, Congress Glance driver
> o
All My Peers,
TL;DR - I will increase adoption of OpenStack by removing governance
RED TAPE and mentoring individuals interested in these objectives.
A brief history of time:
I started my journey in OpenStack by doing a gap analysis of AWS to
OpenkStack at my previous employer Red Hat, Inc.
Adrian,
Makes sense. Do the images have to be built to be mirrored though? Can't
they just be put on the mirror sites fro upstream?
Thanks
-steve
On 3/29/16, 11:02 AM, "Adrian Otto" wrote:
>Steve,
>
>I¹m very interested in having an image locally cached in glance in each
>of the clouds used
A gentle reminder that we're continuing to collect suggestions in the
etherpad for the remainder of the week. As of this email there are '8'
suggestions so far. We look forward to many more over the course of the
week.
Thanks again,
-Sean
On 03/23/2016 07:02 AM, Sean Dague wrote:
> On th
A few months ago, we moved redhat/puppet-pacemaker to
openstack/puppet-pacemaker for some reasons:
* We wanted to take benefits from OpenStack Infra (Gerrit, Zuul,
Jenkins jobs) and improve testing coverage.
Result: we succeed in here, changes in puppet-pacemaker no longer
break TripleO HA jobs,
My immediate question is — when would this be merged? Is it a good idea to
alter this during the final RC week and before mitaka release, rather than
implement this change early in the Newton cycle and let people release their
final release the old way?
--
Kirill Zaitsev
Murano Team
Software E
On Tue, Mar 29, 2016 at 03:19:27PM +0300, Vladimir Kozhukalov wrote:
> > I think this call is too late to change a structure for now. I suggest
> > that we always respect the policy we've accepted, and follow it.
> >
> > If Component Leads role is under a question, then I'd continue the
> > discuss
Steve,
I will defer to the experts in openstack-infra on this one. As long as the
image works without modifications, then I think it would be fine to cache the
upstream one. Practically speaking, I do anticipate a point at which we will
want to adjust something in the image, and it will be nice
Hi all,
As discussed before, our team members want to establish a shared session
between Magnum and Kuryr. We expected a lot of attendees in the session so we
need a large room (fishbowl). Currently, Kuryr has only 1 fishbowl session, and
they possibly need it for other purposes. A solution is
So the advantages I can see with diskimage-builder are:
- we reuse the same tooling that is present in other openstack projects
to generate images, rather than relying on an external image
- it improves the control we have on the contents of the image, instead
of seeing that as a black box. At t
+1
On 29 March 2016 at 11:39, Ryan Hallisey wrote:
> +1
>
> - Original Message -
> From: "Paul Bourke"
> To: [email protected]
> Sent: Tuesday, March 29, 2016 12:10:38 PM
> Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core
> Reviewer
>
> +1
>
On Tue, Mar 29, 2016 at 12:12 PM, Carl Baldwin wrote:
> I've been playing with this a bit on this patch set [1]. I haven't
> gotten very far yet but it has me thinking.
>
> Calico has a similar use case in mind as I do. Essentially, we both
> want to group subnets to allow for aggregation of rou
In multiple occasions in the past, we have had to use version of some
software that's not available yet
in the upstream image for bug fixes or new features (Kubernetes, Docker,
Flannel,...). Eventually the upstream
image would catch up, but having the tool to customize let us push forward
wit
Kirill,
This is prep for Newton. So definitely not rocking the boat when we
have a week left.
-- Dims
On Tue, Mar 29, 2016 at 4:08 PM, Kirill Zaitsev wrote:
> My immediate question is — when would this be merged? Is it a good idea to
> alter this during the final RC week and before mitaka relea
> On Mar 28, 2016, at 6:28 AM, Thierry Carrez wrote:
>
> Hi everyone,
>
> Please find attached in PDF the proposed layout for the various tracks at the
> Design Summit in Austin. I tried to take into account all the talk conflicts
> and the constraints that you communicated, although as alway
1 - 100 of 152 matches
Mail list logo
