Thank you, Thierry & Tony
--Daniel
So could we publish the individual ical files for each meeting too.
That way I could simply add nova.ical to my calendar and avoid other
80 openstack meetings appearing in my schedule.
this answers my second questions.
Regards,
Yatin
On Sat, May 30, 2015 at 3:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
Continuing in Anne's fine tradition, I intend to send these out every
Friday. If you have content you would like to add, or you would like to
be added to the distribution list, please email me directly at
openst...@lanabrindley.com. I've
Hi all,
I just added my 2 cents to a couple of these patches, but in my opinion all of
the existing patches in gerrit for angular tests that were written as part of
the launch instance effort should be finalized and merged prior to any further
reorganization patches going through.
Creating a n
If you are backporting heat templates for Kubernetes, please test each commit
with a bay create followed by a creation of a redis application. For an
example redis application, check out my demo at:
https://github.com/stackforge/kolla/tree/master/demos/magnum
Master is currently broken, I assu
Hey Folks,
I noticed the Kolla functional gate is failing sporadically.
It seems that sometimes an image doesn’t build.
http://logs.openstack.org/75/186475/1/check/check-kolla-functional-f21/8f23913/console.html
One thing that looks off there is barbican is not building a —release image
(I.e.
Hi All,
It turns out we have a few repositories that have been inactive for almost
a year, appear to be dead but don't have any documentation to reflecting
that. (And a lot more that have been dead for over half a year)
format: days since last updated - name
List of stackforge that have not bee
+1 Let’s do it.
From: Matt Fischer
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, May 29, 2015 at 1:46 PM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [puppet] Renaming the IRC channel to
#openstack-puppet
I think the next logical step is to add versioning and predefined tags so
we can distinguish application versions and application status. Right now
the catalog has just information about application without any strict
schema enforced.
The separate problem is to how this information should be handl
Hi everyone,
I just wanted to let you know that the heat-translator project now has IRC
Channel in place - #openstack-heat-translator
Thanks!
Regards,
Sahdev Zala
__
OpenStack Development Mailing List (not for usage quest
I’ve started a doodle poll to vote on the initial IRC meeting
schedule, if you’re interested in helping improve and build up this
catalog please vote for the day/time that works best and get involved!
http://doodle.com/vf3husyn4bdkui8w
The poll will close in one week (June 5). Just sending this r
On Fri, May 29, 2015 at 9:55 AM, Fox, Kevin M wrote:
> As an Op, I really
> really want to replace one image with a new one atomically with security
> updates preapplied. Think shellshock, ghost, etc. It will be basically be
> the same exact image as before, but patched.
On Fri, May 29, 2015 at 1
Excerpts from Anita Kuno's message of 2015-05-29 10:51:35 -0700:
> On 05/29/2015 10:15 AM, Doug Hellmann wrote:
> > Excerpts from Anita Kuno's message of 2015-05-28 17:35:06 -0400:
> >> On 05/28/2015 04:46 PM, Jeremy Stanley wrote:
> >>> On 2015-05-28 13:30:44 -0700 (-0700), Clint Byrum wrote:
> >>
On Fri, May 29, 2015 at 10:42:58AM +0530, yatin kumbhare wrote:
> Great Work!
>
> "New meetings or meeting changes would be proposed in Gerrit, and
> check/gate tests would make sure that there aren't any conflict."
>
> --Will this tell upfront, that in any given day of week, which are all
> mee
On 2015-05-29 17:38:04 -0400 (-0400), Doug Hellmann wrote:
[...]
> This will result in resetting the version numbers to values lower
> than they are currently (12 < 2015), but the distributions can
> prepend an epoch value to their version number to ensure upgrades
> work properly.
[...]
Also for
2015-05-29 21:36 GMT+02:00 Dave Walker :
> Responses inline.
>
> On 29 May 2015 6:15 pm, "Haïkel" wrote:
>>
>> 2015-05-29 15:41 GMT+02:00 Thierry Carrez :
>> > Hi everyone,
>> >
>> > TL;DR:
>> > - We propose to stop tagging coordinated point releases (like 2015.1.1)
>> > - We continue maintaining
This message is a summary of the notes from the “Release Versioning Servers”
discussion held during the release management/QA/infrastructure meetup period
on Friday morning at the summit, along with some commentary I thought of as I
was typing them up. There is no etherpad for that session, but
Hey guys,
One of my top tasks this quarter is to puppetize our ceph environments.
I've already spent some time going over the module, but wanted to start a
conversation around some of the tasks I would like the module to do.
Currently I'm planning on doing the work in the following phases:
Phase
2015-05-29 21:23 GMT+02:00 Ian Cordasco :
>
>
> On 5/29/15, 12:14, "Haïkel" wrote:
>
>>2015-05-29 15:41 GMT+02:00 Thierry Carrez :
>>> Hi everyone,
>>>
>>> TL;DR:
>>> - We propose to stop tagging coordinated point releases (like 2015.1.1)
>>> - We continue maintaining stable branches as a trusted
On Thu, May 28, 2015 at 6:55 AM, Kyle Mestery wrote:
> As part of the team's continuing effort to scale development in Neutron,
> we have officially merged the Lieutenant patch [1]. As the codebase
> continues to grow, this is an attempt to scale the code review load so we
> can grow new core rev
As we chase the release of Fuel 6.1, it's time again to start thinking
about you want to see landing in 7.0
There are a few blueprints [1] already tagged for 7.0 but even more tagged
to next.
If you have something that you would like to see land in 7.0, you should
create a spec and blueprint alon
On 2015-05-29 21:01:23 + (+), Dmitry Borodaenko wrote:
> I think is unnecessarily maximalist. Trust is not an
> all-or-nothing boolean flag: why can't you trust that server to do
> more work at the same level of trust and run another batch of
> user-submitted code?
Because it turns out to
On 2015-05-28 23:19:36 +0200 (+0200), Thomas Goirand wrote:
[...]
> By the way, I was thinking about the sbuild package caching system, and
> thought: how about network mounting /var/cache/pbuilder/aptcache using
> something like Manila (or any other distributed filesystem)? Does infra
> have such
On Fri, May 29, 2015 at 1:48 PM Jeremy Stanley wrote:
> On 2015-05-28 23:09:41 +0200 (+0200), Thomas Goirand wrote:
> > Also, it is my understanding that infra will not accept to use
> > long-living VMs, and prefer to spawn new instances.
>
> Right, after we run arbitrary user-submitted code on a
This message is a summary of the discussion about enabling integration testing
under Python 3 from the summit. The full notes are in
https://etherpad.openstack.org/p/liberty-cross-project-python3 and the spec is
up at https://review.openstack.org/#/c/177375/
tl;dr: Most of our libraries now sup
On 2015-05-29 10:37:43 +0100 (+0100), Derek Higgins wrote:
[...]
> I think the feature in delorean that is most useful is that it
> will continue to maintain a history of usable package repositories
> representing the openstack projects over time, for this we would
> need a long running instance, b
On 2015-05-28 23:09:41 +0200 (+0200), Thomas Goirand wrote:
[...]
> Also, it is my understanding that infra will not accept to use
> long-living VMs, and prefer to spawn new instances.
[...]
Right, after we run arbitrary user-submitted code on a server, we
cease to be able to trust it and so immed
On 2015-05-28 22:45:37 + (+), Fox, Kevin M wrote:
> You could pass the cache through with a volume
Yeah, from the "what can we do with our current CI infrastructure?"
perspective, we would just need a way to identify what bits benefit
from being cached for these particular builds and t
The rotation has gotten a bit thin, and the untriaged bug count growing,
with no one signing up for this past week:
https://etherpad.openstack.org/p/qa-bug-triage-rotation
It would help if every core reviewer could be doing this every other
month. Getting some more sign ups would be very helpf
On 2015-05-29 15:39:20 -0400 (-0400), Mathieu Gagné wrote:
[...]
> Jemery Stanley (fungi) explained to me that previous IRC channel renames
> were done following the Ubuntu procedure. [2] Last rename I remember of
> was #openstack-stable to #openstack-release and it went smoothly without
> any seri
On 05/29/2015 12:55 AM, Feodor Tersin wrote:
> Nicola, i would add some words to Alexandre repsonse.
>
> We (standalone ec2api project guys) have filed some bugs (the main is
> [1]), but we don't know how to fix them since the way Nova's device
> names are moved on is unclear for us. Neither BP, n
Hi Thomos/Mathieu,
Thanks for starting this mail thread. Let's discuss over the IRC as
suggested by Paul.
Thanks
Vikram
On 5/29/15, Paul Michali wrote:
> You can use the VPNaaS IRC channel/time... we don't have much on the agenda
> right now, other than discussion VPN flavors for Liberty, in wh
Good call, it's always at the bottom of my irc client. Might want to
change the channel topic to remind folks to move to #openstack-puppet
Thanks,
Steve Martinelli
OpenStack Keystone Core
From: Mathieu Gagné
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 0
John Garbutt wrote:
On 27 May 2015 at 23:36, Robert Collins wrote:
On 26 May 2015 at 03:37, Chris Friesen wrote:
Hi all,
I've just opened a bug around booting multiple instances at once, and it was
suggested on IRC that I mention it here to broaden the discussion around the
ideal behaviour.
I would love to do this. +2!
On Fri, May 29, 2015 at 1:39 PM, Mathieu Gagné wrote:
> Hi,
>
> We recently asked for our IRC channel (#puppet-openstack) to be logged
> by the infra team. We happen to be the only channel suffixing the word
> "openstack" instead of prefixing it. [1]
>
> I would like
On 29 May 2015 7:41 pm, "Matt Riedemann" wrote:
>
> This, IMO, is about the only time right now that I see doing point
releases on stable as worthwhile. In other words, things have been very
touchy in stable for at least the last 6 months, so in the rare moments of
stability with the gate on sta
Hi,
We recently asked for our IRC channel (#puppet-openstack) to be logged
by the infra team. We happen to be the only channel suffixing the word
"openstack" instead of prefixing it. [1]
I would like to propose renaming our IRC channnel to #openstack-puppet
to better fit the "mold" (convention) a
Responses inline.
On 29 May 2015 6:15 pm, "Haïkel" wrote:
>
> 2015-05-29 15:41 GMT+02:00 Thierry Carrez :
> > Hi everyone,
> >
> > TL;DR:
> > - We propose to stop tagging coordinated point releases (like 2015.1.1)
> > - We continue maintaining stable branches as a trusted source of stable
> > upd
On 5/29/15, 12:14, "Haïkel" wrote:
>2015-05-29 15:41 GMT+02:00 Thierry Carrez :
>> Hi everyone,
>>
>> TL;DR:
>> - We propose to stop tagging coordinated point releases (like 2015.1.1)
>> - We continue maintaining stable branches as a trusted source of stable
>> updates for all projects though
>
Excerpts from Thomas Goirand's message of 2015-05-29 15:11:25 +0200:
> On 05/28/2015 06:41 PM, Devananda van der Veen wrote:
> > Hi all,
> >
> > tl;dr;
> >
> > At the summit, the Ironic team discussed the challenges we've had with
> > the current release model and came up with some ideas to addre
Hi,
We do monitor both IRC and openstack-dev. #murano is our IRC channel. Most
of the time there are someone who can respond quickly. Mirantis and
Telefonica guys are located in Europe so they will respond during US
morning but not during US day time. HP guys are US based so they can
respond more
On 05/29/2015 05:04 AM, John Garbutt wrote:
On 29 May 2015 at 09:00, Sahid Orentino Ferdjaoui
wrote:
On Fri, May 29, 2015 at 08:47:01AM +0200, Jens Rosenboom wrote:
As the discussion in https://review.openstack.org/179569 still
continues about whether this is "just" a bug fix, or an API change
We have several library projects outside of Oslo that need releases anyway, and
since some of them are blocking work we want to do to drop the “oslo” namespace
package I have collected a list and will tag releases on Monday morning. I have
confirmed all of these releases with the PTLs of the rel
On 5/29/2015 10:00 AM, David Medberry wrote:
On Fri, May 29, 2015 at 7:41 AM, Thierry Carrez mailto:thie...@openstack.org>> wrote:
If you were a consumer of those and will miss them, please explain why.
In particular, please let us know how consuming that version (which was
only m
I believe that current app store approach uses only image name rather then
ID. So you can replace image with a new one without affecting application
definitions. Both Heat and Murano can use just image name without IDs. I
think it should be supported in artifact repository too.
As for other then
On 05/28/2015 05:11 AM, Gal Sagie wrote:
> Hi Kevin,
>
> The main idea that i tried to express, is we need a course of action after
> the discussions, i understand that we want to discuss high level points
> but we still need to decide on a follow up plan, because otherwise this is
> all wasted.
>
On 05/29/2015 10:15 AM, Doug Hellmann wrote:
> Excerpts from Anita Kuno's message of 2015-05-28 17:35:06 -0400:
>> On 05/28/2015 04:46 PM, Jeremy Stanley wrote:
>>> On 2015-05-28 13:30:44 -0700 (-0700), Clint Byrum wrote:
>>> [...]
Do we already have this hidden somewhere, or would it make sen
Gorka Eguileor wrote:
On Thu, May 28, 2015 at 10:51:35AM -0700, Joshua Harlow wrote:
Btw, if u *do not* want to do a spec (using [1]) or blueprint let me know
and I'll probably make a spec so that we can ensure (and agree on) the
semantics of this because the specifics of what 'cancel' or 'abort
Hi all,
Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work
is being somewhat driven by the etherpad at [2]. But this etherpad
doesn't have a section for libvirt / vif driver changes. The log at [1]
briefly touched on this, but moved on after noting that Dan PB had
disba
2015-05-29 15:41 GMT+02:00 Thierry Carrez :
> Hi everyone,
>
> TL;DR:
> - We propose to stop tagging coordinated point releases (like 2015.1.1)
> - We continue maintaining stable branches as a trusted source of stable
> updates for all projects though
>
Hi,
I'm one of the main maintainer of the p
Matt Fischer wrote:
Was the intent here to allow bringing up new
compute hosts without them being enabled? If so there's another flag
that could be set to manage that state.
Mathieu posited the following intent in the review:
"It was used in some active/passive setup (as stated in the bug repo
I've ran into the opposite problem though with Glance. As an Op, I really
really want to replace one image with a new one atomically with security
updates preapplied. Think shellshock, ghost, etc. It will be basically be the
same exact image as before, but patched. Referencing local ID's explici
On 2015-05-29 12:28:37 -0400 (-0400), Doug Hellmann wrote:
> First, where do you hang out on IRC? I couldn’t find a channel
> that looked like it had any population, and there’s nothing
> mentioned on https://wiki.openstack.org/wiki/Murano
[...]
https://wiki.openstack.org/wiki/IRC says it's #mura
On 2015-05-29 16:30:12 +0100 (+0100), Dave Walker wrote:
> This is generally my opinion as-well, I always hoped that *every*
> commit would be considered a release rather than an arbitrary
> tagged date.
[...]
If we switch away from lockstep major/minor release versioning
anyway (again separate di
Hi Kevin,
I don't suggest to use random IDs as artifact identifiers in the community
app catalog. Of course we will need to have some globally unique names
there (my initial idea on that is to have a combination of fully-qualified
namespace-based name + version + signature) - and such names should
Hi, Murano team!
First, where do you hang out on IRC? I couldn’t find a channel that looked like
it had any population, and there’s nothing mentioned on
https://wiki.openstack.org/wiki/Murano
I’m trying to figure out whether the upcoming Oslo library releases are going
to break your gate. Both
On 2015-05-29 17:50:01 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
> if we attempt to fix a security issue that has a backwards
> incompatible fix, then we are forced in introducing a new
> configuration option to opt-in the new secure world.
[...]
To my knowledge that's how we've handled these in
On Fri, May 29, 2015 at 8:11 AM, Thomas Goirand wrote:
> On 05/28/2015 06:41 PM, Devananda van der Veen wrote:
> > Hi all,
> >
> > tl;dr;
> >
> > At the summit, the Ironic team discussed the challenges we've had with
> > the current release model and came up with some ideas to address them.
> > I
On 05/29/2015 06:27 AM, John Garbutt wrote:
On 27 May 2015 at 23:36, Robert Collins wrote:
On 26 May 2015 at 03:37, Chris Friesen wrote:
Basically the problem is this:
When booting up instances, nova allows the user to specify a "min count" and
a "max count". So logically, this request sh
Hi Lily,
Could you let us know how and what tests you are running for lbaasv2? To my
understanding, I don't see all the api/scenario tests for lbaasv2 are
skipped. However, there are documents about neutron lbaasv2 and API tests
and they are documented [1][2] respectively.
[1] https://wiki.openst
Hi Gal,
Thanks for starting this thread, and I'm sorry not to have met you
during the summit.
Vancouver was my first summit, and I very much enjoyed it. My
reflection is that I came to the summit with two overall expectations,
of which one proved correct and one false.
The correct expecta
I have a question I'd like to ask offline... Can someone from the ironic
team ping me? Have a question about pxe...
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openst
You can use the VPNaaS IRC channel/time... we don't have much on the agenda
right now, other than discussion VPN flavors for Liberty, in which it would
be good to discuss BGP VPN and Edge VPN.
Regards,
Paul Michali (pc_m)
On Fri, May 29, 2015 at 11:08 AM wrote:
> Hi everyone,
>
> As a follow-u
On 29 May 2015 at 16:25, Matthew Thode wrote:
>
> for release notes just do git log between commit hashes?
>
For Ubuntu, I wrote a tool to do just this and generate a Debian style
changelog (later cleaned up quite a lot by adamg!). It parses the git
log looking for LP bug references and uses th
Hi Alexander,
Sweet. I'll have to kick the tires on the current state of Liberty soon. :)
Reference by artifact IDs is going to be problematic I think. How do you
release a generic set of resources to the world that reference specific
randomly generated ID's?
What about by Name? If not, then i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/29/2015 05:26 PM, Thierry Carrez wrote:
> Ihar Hrachyshka wrote:
>> What about release notes? How can we now communicate some changes
>> that require operator consideration or action?
>
> Arguably each and every "change requiring operator cons
On 5/29/2015 10:30 AM, Dave Walker wrote:
On 29 May 2015 at 14:41, Thierry Carrez wrote:
Hi everyone,
TL;DR:
- We propose to stop tagging coordinated point releases (like 2015.1.1)
- We continue maintaining stable branches as a trusted source of stable
updates for all projects though
Long v
I found some code in plugins/ml2/managers.py. There writes "super(TypeManager,
self).__init__('neutron.ml2.type_drivers',". The "neutron.ml2.type_drivers" is
namespace by document. What does namespace mean? Can I write a random
namespace linke 'abcdef'?__
On 29 May 2015 at 14:41, Thierry Carrez wrote:
> Hi everyone,
>
> TL;DR:
> - We propose to stop tagging coordinated point releases (like 2015.1.1)
> - We continue maintaining stable branches as a trusted source of stable
> updates for all projects though
>
> Long version:
>
> At the "stable branch
On 05/29/2015 10:18 AM, Ihar Hrachyshka wrote:
> What about release notes? How can we now communicate some changes that
> require operator consideration or action?
>
> Ihar
>
> On 05/29/2015 03:41 PM, Thierry Carrez wrote:
>> Hi everyone,
>
>> TL;DR: - We propose to stop tagging coordinated poin
Ihar Hrachyshka wrote:
> What about release notes? How can we now communicate some changes that
> require operator consideration or action?
Arguably each and every "change requiring operator consideration or
action" mentioned in these release notes is a failure in the stable
branch process -- this
Neil Jerram wrote:
>
>
> On 29/05/15 14:41, Thierry Carrez wrote:
>> Hi everyone,
>>
>> TL;DR:
>> - We propose to stop tagging coordinated point releases (like 2015.1.1)
>> - We continue maintaining stable branches as a trusted source of stable
>> updates for all projects though
> [...]
>
> I in
Hello,
How Monasca is getting authenticated through Keystone?
The reason of asking this is: Monasca is in Java, whereas other services
(like Cinder) uses the keystone-middleware-authentication (when configured)
through api-paste.ini. And the middleware is in python.
Does Monasca uses some othe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
What about release notes? How can we now communicate some changes that
require operator consideration or action?
Ihar
On 05/29/2015 03:41 PM, Thierry Carrez wrote:
> Hi everyone,
>
> TL;DR: - We propose to stop tagging coordinated point releases
>
On 29/05/15 14:41, Thierry Carrez wrote:
Hi everyone,
TL;DR:
- We propose to stop tagging coordinated point releases (like 2015.1.1)
- We continue maintaining stable branches as a trusted source of stable
updates for all projects though
[...]
I initially misunderstood your email as saying th
On Fri, May 29, 2015 at 7:41 AM, Thierry Carrez
wrote:
> If you were a consumer of those and will miss them, please explain why.
> In particular, please let us know how consuming that version (which was
> only made available every n months) is significantly better than picking
> your preferred ti
Hi everyone,
As a follow-up to discussions last week on a BGP VPN interconnection API
and the work started with the people already involved, we are going to
hold IRC meetings to discuss how to progress the different pieces of
work, in particular on the API itself [1] and its implementation+dri
On 05/29/2015 09:44 AM, Matt Riedemann wrote:
>
>
> On 5/29/2015 8:41 AM, Thierry Carrez wrote:
>> Hi everyone,
>>
>> TL;DR:
>> - We propose to stop tagging coordinated point releases (like 2015.1.1)
>> - We continue maintaining stable branches as a trusted source of stable
>> updates for all pro
On 05/29/2015 07:56 AM, Thomas Goirand wrote:
> Hi,
>
> Currently, in the global requirements, we have:
> sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
>
> However, like it or not, sphinx 1.3 will soon reach Debian unstable.
> Already, I see something broken with it:
> https://gist.github.com/mitya57/1643a7
On 5/29/2015 8:41 AM, Thierry Carrez wrote:
Hi everyone,
TL;DR:
- We propose to stop tagging coordinated point releases (like 2015.1.1)
- We continue maintaining stable branches as a trusted source of stable
updates for all projects though
Long version:
At the "stable branch" session in Vanc
I'd like them to default to enabled as well since it matches the other
modules as you said. Was the intent here to allow bringing up new compute
hosts without them being enabled? If so there's another flag that could be
set to manage that state.
As for the patch itself, we need to change it for al
We are currently reviewing a patch[0] which will result in a change to
the way Nova services are managed by default. Previously services were
set to 'Disabled' by default, and had to be manually enabled in the
manifests, this change will make the default value 'Enabled'.
The consensus is that
Excerpts from Anita Kuno's message of 2015-05-28 17:35:06 -0400:
> On 05/28/2015 04:46 PM, Jeremy Stanley wrote:
> > On 2015-05-28 13:30:44 -0700 (-0700), Clint Byrum wrote:
> > [...]
> >> Do we already have this hidden somewhere, or would it make sense to
> >> maybe add this as something in openst
Hi everyone,
TL;DR:
- We propose to stop tagging coordinated point releases (like 2015.1.1)
- We continue maintaining stable branches as a trusted source of stable
updates for all projects though
Long version:
At the "stable branch" session in Vancouver we discussed recent
evolutions in the stab
Excerpts from Thierry Carrez's message of 2015-05-29 12:12:51 +0200:
> Devananda van der Veen wrote:
> > [...]
> > The alternative we discussed:
> > - use feature branches for risky / large work, keeping total # of
> > branches small, and rebasing them regularly on master
> > - keep trunk moving qu
On 05/28/2015 06:41 PM, Devananda van der Veen wrote:
> Hi all,
>
> tl;dr;
>
> At the summit, the Ironic team discussed the challenges we've had with
> the current release model and came up with some ideas to address them.
> I had a brief follow-up conversation with Doug and Thierry, but I'd
> li
Hi,
Currently, in the global requirements, we have:
sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
However, like it or not, sphinx 1.3 will soon reach Debian unstable.
Already, I see something broken with it:
https://gist.github.com/mitya57/1643a7c1666b650a0de5
(if you didn't notice, that's sphinxcontrib-pr
On 05/28/2015 05:32 PM, James Slagle wrote:
Then I'm +1 for running Puppet with 'ensure => latest' first and then 'yum
>update -y'. Seems ideal solution from my point of view.
How would this solve the library update problem though?. If a new
version of a library is released to address a securit
Le 29/05/2015 14:27, John Garbutt a écrit :
On 27 May 2015 at 23:36, Robert Collins wrote:
On 26 May 2015 at 03:37, Chris Friesen wrote:
Hi all,
I've just opened a bug around booting multiple instances at once, and it was
suggested on IRC that I mention it here to broaden the discussion ar
On 27 May 2015 at 23:36, Robert Collins wrote:
> On 26 May 2015 at 03:37, Chris Friesen wrote:
>>
>> Hi all,
>>
>> I've just opened a bug around booting multiple instances at once, and it was
>> suggested on IRC that I mention it here to broaden the discussion around the
>> ideal behaviour.
>>
>>
On 2015-05-29 11:47:36 +0200 (+0200), Thierry Carrez wrote:
[...]
> As far as vulnerability management goes, we already publish the
> "master" fix as part of the advisory, so people can easily find
> that. The only thing the VMT might want to reconsider is: when an
> issue is /only/ present in the
On 29 May 2015 at 09:00, Sahid Orentino Ferdjaoui
wrote:
> On Fri, May 29, 2015 at 08:47:01AM +0200, Jens Rosenboom wrote:
>> As the discussion in https://review.openstack.org/179569 still
>> continues about whether this is "just" a bug fix, or an API change
>> that will need a new micro version,
Hi Kevin,
Has the Glance Artifact Repository implemented enough bits to have Heat
> and/or Murano artefacts yet?
>
Most of the code is there already, couple of patchsets are still on review
but we'll land them soon. L1 is a likely milestone to have it ready in
master.
Also, has there been an
Thanks,
I updated nodepool and nodepool scripts and now it seems the image is
building.
Eduard
On Thu, May 28, 2015 at 6:39 PM, Jeremy Stanley wrote:
> On 2015-05-28 11:58:43 +0300 (+0300), Eduard Matei wrote:
> > We had some issues with jenkins/devstack so i updated both the jenkins
> > versi
Devananda van der Veen wrote:
> [...]
> The alternative we discussed:
> - use feature branches for risky / large work, keeping total # of
> branches small, and rebasing them regularly on master
> - keep trunk moving quickly for smaller / less risky / refactoring changes
> - "slow down" for a week o
Hi all,
I try to test neutron LBaaS with tempest, but find all the API and scenario
test cases related to it are skipped. Is there a way to enable these test
cases? I have LBaaS service enabled already. Also, is there any detailed
document about lbaasv2?
Thanks.
Best regards,
Lily Xing(邢莉莉)
Did the trick! Thanks
for records, commands typed:
workon fuel-web
cd fuel-web/nailgun
pip install -r requirements.txt
pip install nodeenv
nodeenv nenv
source nenv/bin/activate
npm install -g gulp bower
gulp bower
scp -r static/ root@:/tmp/
master# dockerctl copy /tmp/static nailgun:/usr/
Lucas Alvares Gomes wrote:
>>> - OpenStack coordinated releases are taken from latest independent release
>>> - that release will then get backports & stable maintenance, other
>>> independent releases don't
>>
>> So no stable branch for other independent releases? What if serious security
>> issue
On 29/05/15 02:54, Steve Kowalik wrote:
On 29/05/15 06:41, Haïkel wrote:
Here's the main script to rebuild a RPM package.
https://github.com/openstack-packages/delorean/blob/master/scripts/build_rpm.sh
The script basically uses rpmbuild to build packages, we could have a
build_deb.sh that use
On 28/05/15 20:58, Paul Belanger wrote:
On 05/27/2015 05:26 PM, Derek Higgins wrote:
On 27/05/15 09:14, Thomas Goirand wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
tl;dr:
- - We'd like to push distribution packaging of OpenStack on upstream
gerrit with reviews.
- - The int
On 28/05/15 22:09, Thomas Goirand wrote:
On 05/28/2015 02:53 PM, Derek Higgins wrote:
On 28/05/15 12:07, Jaume Devesa wrote:
Hi Thomas,
Delorean is a tool to build rpm packages from master branches (maybe any
branch?) of OpenStack projects.
Check out here:
https://www.rdoproject.org/packa
1 - 100 of 108 matches
Mail list logo
