Hi Vikas,
> >The question is what you mean by multi-tenancy, if you mean that different
> >tenants each control their own bare-metal
> >server then Kuryr already support this. (by tenant credential configuration)
>
>I understand kuryr can configure with tenant credential, but we still need
> Okay, so I initially thought we weren't making much progress on this
> discussion, but after some more thought and reading of the existing PoC,
> we're (maybe?) less far apart than I initially thought.
>
> I think there are kind of three different designs being discussed.
>
> 1) Rewrite a bunch
This bug and another related block bug:
https://bugs.launchpad.net/nova/+bug/1536509 been merged recently, PCI-CI now
is back online.
Regards
Yongli He
-Original Message-
From: Nikola Đipanov [mailto:[email protected]]
Sent: Wednesday, January 20, 2016 10:41 PM
To: OpenStack Developm
Hi Jeo,
This error occurred when installing devstack on node2.
Best regards,
Yipei
On Wed, Jan 27, 2016 at 3:13 PM, Yipei Niu wrote:
>
> -- Forwarded message --
> From: Yipei Niu
> Date: Tue, Jan 26, 2016 at 8:42 PM
> Subject: Re: [tricircle] Playing Tricircle with Devstack
>
Yes, I have created custom iso with debug output. It didn't help, so
another one with strace was created.
On Jan 27, 2016 00:56, "Alex Schultz" wrote:
> On Tue, Jan 26, 2016 at 2:16 PM, Stanislaw Bogatkin
> wrote:
> > When there is too high strata, ntpdate can understand this and always
> write
Hi Gal,
I missed the mail and the meeting...
I imported the ics file[1] from eavesdrop site before Christmas and since
January it seems the schedule and the reality are switched.
Can it be that the calendar has to be updated, or it is because I am completely
unable to deal with organization tool
>
> Hi Gyorgy,
>
Hi Kevin,
> I'll definitely give this a look and thanks for sharing. I would like to ask
> however why you found OpenStack-Anisble overly complex so much so that
> you've taken on the complexity of developing a new installer all together? I'd
> love to understand the issues you
> On 01/26/2016 11:32 AM, Gyorgy Szombathelyi wrote:
> > Hello!
> >
> > I just want to announce a new installer for OpenStack:
> > https://github.com/DoclerLabs/openstack
> > It is GPLv3, uses Ansible (currently 1.9.x, 2.0.0.2 has some bugs which has
> to be resolved), has lots of components inte
Looks like we can use user_data and cloud-init to do this stuff.
Adding the following content into user_data.txt and launch instance like
this: nova boot --user-data user_data.txt ...,
the instance will shutdown after boot is finished.
power_state:
mode: poweroff
message: Bye Bye
You can find
Hi, Yipei,
The issue is still caused by the change in DevStack. When the command
"openstack volume type create --property volume_backend_name=lvmdriver-1
lvmdriver-1" is executed in DevStack, the exported region name (i.e, RegionOne)
is used, so the request was sent to RegionOne, but the volum
Hi Jaume,
Not sure what is the problem, we are doing alternating meetings now, but
maybe
we switched the weeks as we didn't have a meeting at holidays week
(Christmas).
I am usually trying to send email at least a day before to the mailing
list, next week the meeting is
happening at Monday (1500
> the API has L2Insertions that each have a position. The current API
> therefore only expects a single list of L2Insertions on a single VM. It
> seems wrong to attach classifiers to the L2Insertion object... on the other
> hand, since the model assumes the Service Function leaves the traffic
> unm
On Tue, Jan 26, 2016, at 07:46 AM, Christian Berendt wrote:
> After offloading a shelved instance the freed compute resources are
> still accounted.
>
> I think it makes sense to make this behavior configurable. We often have
> the request to not account the freed compute resources after an
>
Hi,
You can find the meeting minutes of Vitrage meeting:
http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-27-09.00.html
Meeting log:
http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-27-09.00.log.html
See you next week,
Ifat.
Thank you so much. Eron. This really helps me a lot!!
Tan
From: Kuvaja, Erno [mailto:[email protected]]
Sent: Tuesday, January 26, 2016 8:34 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova][glance][cinder][neutron]How to make use of
x-openstack
But you've used 'logger -t ntpdate' - this is can fail again and logs can
be empty again.
My opinion we should use output redirection to the log-file directly.
On Wed, Jan 27, 2016 at 11:21 AM, Stanislaw Bogatkin wrote:
> Yes, I have created custom iso with debug output. It didn't help, so
> an
On 1/27/2016 9:40 AM, Tan, Lin wrote:
Thank you so much. Eron. This really helps me a lot!!
Tan
*From:*Kuvaja, Erno [mailto:[email protected]]
*Sent:* Tuesday, January 26, 2016 8:34 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [nova][glance
Hi Gord,
Could you please kindly suggest how to proceed further on the below issue as
we are somewhat blocked in our development activity due to the wildcard issue.
With Best Regards
Raghunath Dudyala
Tata Consultancy Services Limited
Mailto: [email protected]
Website: http://www.tcs.com
_
I see no follow-up to Swann's question so let me elaborate why this issue
is important for the LMA plugins.
First I need to explain what was our release schedule for the LMA plugins
during the MOS 7.0 cycle:
- New features were done on the master branch which was only compatible
with MOS 7.0.
- We
> -Original Message-
> From: Matt Riedemann [mailto:[email protected]]
> Sent: Wednesday, January 27, 2016 9:56 AM
> To: [email protected]
> Subject: Re: [openstack-dev] [nova][glance][cinder][neutron]How to make
> use of x-openstack-request-id
>
>
>
> On 1/27/20
>But you've used 'logger -t ntpdate' - this is can fail again and logs can
be empty again.
What do you mean by 'fall again'? Piping to logger uses standard blocking
I/O - logger gets
all the output it can reach, so it get all output strace will produce. If
ntpdate will hang for some
reason - we sho
Thanks for the vote of confidence all, I look forward to expanding
what I'm working on.
Cheers,
Sachi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subj
> -Original Message-
> From: Flavio Percoco [mailto:[email protected]]
> Sent: Monday, January 25, 2016 3:07 PM
> To: [email protected]
> Subject: Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on
> the
> idea to move it forward
>
> On 20/01/16 13:23 -0430
On 1/26/2016 5:55 AM, Avishay Traeger wrote:
OK great, thanks! I added a suggestion to the etherpad as well, and
found this link helpful: https://review.openstack.org/#/c/266095/
On Tue, Jan 26, 2016 at 1:37 AM, D'Angelo, Scott mailto:[email protected]>> wrote:
There is currently no
I'm always happy to add new cores :)
+1 for Kairat. He has been working really hard and the huge number of
high-quality reviews and commits is a good proof of this. Welcome Kairat!
+1 for Brian. He is one of the most experienced technical specialists and he's
a well-known member in the community.
On Wed, Jan 27, 2016 at 1:01 PM, Matt Riedemann
wrote:
> I've replied on https://review.openstack.org/#/c/266095/ and the related
> cinder change https://review.openstack.org/#/c/272899/ which are adding a
> new key to the volume connector dict being passed around between nova and
> cinder, whic
On Wed, Jan 27, 2016, at 05:47 AM, Kuvaja, Erno wrote:
> > -Original Message-
> > From: Matt Riedemann [mailto:[email protected]]
> > Sent: Wednesday, January 27, 2016 9:56 AM
> > To: [email protected]
> > Subject: Re: [openstack-dev] [nova][glance][cinder][neutro
I think we shouldn't depend on the other services like Syslog and logger
trying to catch the problem and it is better to create the logs ourselves.
On Wed, Jan 27, 2016 at 1:49 PM, Stanislaw Bogatkin
wrote:
> >But you've used 'logger -t ntpdate' - this is can fail again and logs can
> be empty
On 1/27/2016 11:22 AM, Avishay Traeger wrote:
On Wed, Jan 27, 2016 at 1:01 PM, Matt Riedemann
mailto:[email protected]>> wrote:
I've replied on https://review.openstack.org/#/c/266095/ and the
related cinder change https://review.openstack.org/#/c/272899/ which
are adding
On 27/01/16 10:34 +1300, Fei Long Wang wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi team,
As you know, I'm working on Zaqar team as PTL in Mitaka and it's a
time-consuming work. So my focus shifted for a bit but I'm now trying to
balance my time. I'd rather stay in the team if there
On 27/01/16 11:00 +, Kuvaja, Erno wrote:
-Original Message-
From: Flavio Percoco [mailto:[email protected]]
Sent: Monday, January 25, 2016 3:07 PM
To: [email protected]
Subject: Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the
idea to move it forw
> It makes for a crappy user experience. Crappier than the crappy user
> experience that OpenStack API users already have because we have done a
> crappy job shepherding projects in order to make sure there isn't
> overlap between their APIs (yes, Ceilometer and Monasca, I'm looking
> directly at y
On 26/01/16 09:11 +, Daniel P. Berrange wrote:
On Sun, Jan 24, 2016 at 12:00:16AM +0200, Duncan Thomas wrote:
I guess my wisdom would be 'why'? What does this enable you to do that you
couldn't do with similar ease with the formats we have and are people
trying to do that frequently.
We've
On 27/01/16 08:20 -0430, Flavio Percoco wrote:
On 26/01/16 09:11 +, Daniel P. Berrange wrote:
On Sun, Jan 24, 2016 at 12:00:16AM +0200, Duncan Thomas wrote:
I guess my wisdom would be 'why'? What does this enable you to do that you
couldn't do with similar ease with the formats we have and
Starting with stable/liberty, each project now owns when to do point
releases for their stable branches (rather than a large coordinated
stable branch point release that the stable-maint-core team does).
There are a couple of core projects which have not done a stable/liberty
point release sin
On Wed, Jan 27, 2016 at 08:32:58AM -0430, Flavio Percoco wrote:
> On 27/01/16 08:20 -0430, Flavio Percoco wrote:
> >On 26/01/16 09:11 +, Daniel P. Berrange wrote:
> >>On Sun, Jan 24, 2016 at 12:00:16AM +0200, Duncan Thomas wrote:
> >>>I guess my wisdom would be 'why'? What does this enable you
Hey folks,
After four months and 80+ gerrit reviews, the security hardening configurations
provided by the openstack-ansible-security role are now integrated with
OpenStack-Ansible! The Jenkins gate jobs for OpenStack-Ansible are already
applying these configurations by default.
Documentation
Hi
We are seeing an error in task execution , transaction is rollbacked an I
believe its causing problems in deletion (fk violation)
Shouldn't we have some kind of retry mechanism for deadlock ?
Will be happy to get any thoughts on the matter
Thanks
[root@s54-0 ~(keystone_cb2)]# mistral task-ge
On 01/26/2016 09:05 PM, Ben Nemec wrote:
On 01/25/2016 04:36 PM, Dan Prince wrote:
On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote:
On 01/22/2016 06:19 PM, Dan Prince wrote:
On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote:
So I haven't weighed in on this yet, in part because I was on
va
On 27 January 2016 at 08:10, Tzu-Mainn Chen wrote:
> > Okay, so I initially thought we weren't making much progress on this
> > discussion, but after some more thought and reading of the existing PoC,
> > we're (maybe?) less far apart than I initially thought.
> >
> > I think there are kind of th
Hi,
I see that tasks.yaml is going to be deprecated in the future MOS versions
[1]. I've got one question regarding the ordering of tasks between
different plugins.
With tasks.yaml, it was possible to coordinate the execution of tasks
between plugins without prior knowledge of which plugins were i
Top posting since better scheduler testing just got brought up during
the midcycle meetup, so it might be useful to re-kindle this thread.
Sean (Dague) brought up that there is some infrastructure already that
could help us do what you propose bellow, but work may be needed to make
it viable for p
On Tue, 2016-01-26 at 14:05 -0600, Ben Nemec wrote:
> On 01/25/2016 04:36 PM, Dan Prince wrote:
> > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote:
> > > On 01/22/2016 06:19 PM, Dan Prince wrote:
> > > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote:
> > > > > So I haven't weighed in on th
On 27 January 2016 at 06:40, Matt Riedemann
wrote:
> On 1/27/2016 11:22 AM, Avishay Traeger wrote:
>
>>
>> I agree with you. Actually, I think it would be more correct to have
>> Cinder store it, and not pass it at all to terminate_connection().
>>
>>
> That would be ideal but I don't know if ci
Yay Sachi!
On Jan 27, 2016 05:01, "Sachi King" wrote:
> Thanks for the vote of confidence all, I look forward to expanding
> what I'm working on.
>
> Cheers,
> Sachi
>
> __
> OpenStack Development Mailing List (not for usage
On 26 January 2016 at 16:01, Ben Nemec wrote:
> On 01/26/2016 03:46 AM, Steven Hardy wrote:
> > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote:
> >> On 01/25/2016 03:56 PM, Steven Hardy wrote:
> >>> On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote:
> So I haven't weighed
Disclaimer: I'm from Kolla.
Well, you will see these benefits when you'll try to perform upgrade:)
that's the tricky part about containers - they become really useful
after 6 months. Without them you'll end up having to upgrade every
service at the very same time, and that's disruptive at best,
di
On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote:
> On 01/26/2016 09:05 PM, Ben Nemec wrote:
> > On 01/25/2016 04:36 PM, Dan Prince wrote:
> > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote:
> > > > On 01/22/2016 06:19 PM, Dan Prince wrote:
> > > > > On Fri, 2016-01-22 at 11:24 -0600, Be
Looking for 5 more core reviewers to step forward and take on an OpenStack
service and a infrastructure service prior to the midcycle.
If you can't finish the openstack service in time and get it merged, that's ok
- please just get a patch in the review queue with your work.
For the infrastruct
On 2016-01-27 09:42:30 +0100 (+0100), Jaume Devesa wrote:
> I missed the mail and the meeting...
>
> I imported the ics file[1] from eavesdrop site before Christmas and since
> January it seems the schedule and the reality are switched.
>
> Can it be that the calendar has to be updated, or it is
Thank you for your reply.
This approach has 3 disadvantages that I can think of:
1. An image might have configurations processes that only happen on the
first boot and require user input. This is a probable use-case
2. Not all images support cloud-init
3. This creates an unnecessary load on the c
The Kolla community is pleased to announce the release of Mitaka milestone #2.
We did not announce the release of Mitaka-1 because the PTL was unavailable to
tag the release. As a result, we are announcing changes that also occured in
the Mitaka-1 tag here. For further releases of Kolla, we h
Hi, Dmitry.
I also would like to add `set -o pipefail` to the list as in a fantastic
Youtube talk 'The Functional Tao of Bash - Garrett Smith'[0].
[0] https://www.youtube.com/watch?v=yD2ekOEP9sU
On Tue, Jan 26, 2016 at 1:09 PM, Dmitry Bilunov
wrote:
> Hello.
>
> Recently we had a typo[1], whic
> On Wed, 2016-01-27 at 09:36 -0500, Dan Prince wrote:
> > On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote:
> > > On 01/26/2016 09:05 PM, Ben Nemec wrote:
> > > > On 01/25/2016 04:36 PM, Dan Prince wrote:
> > > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote:
> > > > > > On 01/22/2016
On Wed, 2016-01-27 at 09:36 -0500, Dan Prince wrote:
> On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote:
> > On 01/26/2016 09:05 PM, Ben Nemec wrote:
> > > On 01/25/2016 04:36 PM, Dan Prince wrote:
> > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote:
> > > > > On 01/22/2016 06:19 PM, Da
On 01/27/2016 12:53 PM, gordon chung wrote:
It makes for a crappy user experience. Crappier than the crappy user
experience that OpenStack API users already have because we have done a
crappy job shepherding projects in order to make sure there isn't
overlap between their APIs (yes, Ceilometer an
Hi Andrew,
Am 27.01.2016 um 10:38 schrieb Andrew Laski:
> 1. This allows for a poor experience where a user would not be able to
> turn on and use an instance that they already have due to overquota.
> This is a change from the current behavior where they just can't create
> resources, now someth
Multiple cancels, and I'll be on a plane.
Thanks,
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-
I've got proposal from mos-linux team about switch to sntp instead of
ntpdate due to ntpdate deprecation. It looks nice enough for me but we
already had similar problems with sntp before switching to ntpdate.
Does anyone vote against switching to sntp?
On Wed, Jan 27, 2016 at 2:25 PM, Maksim Malch
Hi All,
We briefly discussed feature tracking in this weeks tripleo meeting. I
would like to provide a way for downstream consumers (and ourselves) to
track new features as they get implemented. The main things that came
out of the discussion is that people liked the spec-lite process that
th
We are overjoyed to announce the release of:
networking-sfc 1.0.0: API's and implementations to support Service
Function Chaining in Neutron.
This release is part of the independent release series.
With source available at:
http://git.openstack.org/cgit/openstack/networking-sfc
With packag
Thanks very much for the update, Ihar, much appreciated!
On 01/26/2016 01:19 PM, Ihar Hrachyshka wrote:
Jay Pipes wrote:
Hey Sean,
Tomorrow morning UTC, we'll be discussing Neutron topics at the Nova
mid-cycle. Wondering if you might give us a quick status update on
where we are with the Neu
Hi,
I would like to quickly announce the creation of a new project called
Ironic Staging Drivers.
What the Ironic Staging Drivers project is?
-
As context, in the Tokyo design summit it was decided that drivers in the
Ironic tree will
On 26.01.2016 22:18, Kyrylo Galanov wrote:
> Hello Bogdan,
>
> I hope I am not the one of the context. Why do we separate fixtures for
> Noop tests from the repo?
> I can understand if while noop test block was carried out to a separate
> repo.
>
I believe fixtures normally are downloaded by the
As someone that has upgraded rdo clouds on multiple occasions, I concur. Its
way easier to upgrade a whole cloud, (or even pieces of a cloud are possible)
with properly isolated containers instead of rpms. Thats the case where
containers really shine, and you don't experience it until you try an
On 27/01/2016 10:51 AM, Jay Pipes wrote:
> On 01/27/2016 12:53 PM, gordon chung wrote:
>>> It makes for a crappy user experience. Crappier than the crappy user
>>> experience that OpenStack API users already have because we have done a
>>> crappy job shepherding projects in order to make sure the
Vladislav Kuzmin said on Tue, Dec 15, 2015 at 04:26:32PM +0300:
> I want to specify all my option in yaml file, because it is much more
> readable. But I must use ini file, because oslo.log using
> logging.config.fileConfig for reading the config file (
> https://github.com/openstack/oslo.log/blob/
On 01/27/2016 10:51 AM, Jay Pipes wrote:
> On 01/27/2016 12:53 PM, gordon chung wrote:
>>> It makes for a crappy user experience. Crappier than the crappy user
>>> experience that OpenStack API users already have because we have done a
>>> crappy job shepherding projects in order to make sure the
This appears to have gone away this morning. I ran clean.sh and removed
monotonic.
The next run of stack.sh installed version 0.6 of monotonic and I no longer
see this exception.
Bob Hansen
z/VM OpenStack Enablement
From: Bob Hansen/Endicott/IBM@IBMUS
To: "openstack-dev"
Date: 01/26/
On 01/27/2016 03:36 PM, Dan Prince wrote:
On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote:
On 01/26/2016 09:05 PM, Ben Nemec wrote:
On 01/25/2016 04:36 PM, Dan Prince wrote:
On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote:
On 01/22/2016 06:19 PM, Dan Prince wrote:
On Fri, 2016-01-22
Hi,
Thanks for the responses. Putting it in a small example
def flow_factory(tmp):
return lf.Flow('resume from backend example').add(
TestTask(name='first', test=tmp),
InterruptTask(name='boom'),
TestTask(name='second', test="second task"))
class TestTask(task.Task):
pn kk wrote:
Hi,
Thanks for the responses. Putting it in a small example
def flow_factory(tmp):
return lf.Flow('resume from backend example').add(
TestTask(name='first', test=tmp),
InterruptTask(name='boom'),
TestTask(name='second', test="second task"))
class T
Hello everyone,
I created another BP for Newton release regarding glance community image
visibility based on Louis Taylor's original BP. I will continue working on
feature. Before I upload our implementation, it will be wonderful if anyone
in glance community can review and approve the BP. It ca
+1 on sharing/outlining migration script form v1 to v2. It will help lot of
teams.
Thanks,
Vivek
On 1/26/16, 6:58 PM, "Kevin Carter" wrote:
>I know that Neutron LBaaS V1 is still available in Liberty and functional, and
>at this point I assume its in Mitaka (simply judging the code not
On 27/01/16 12:16 -0500, Emilien Macchi wrote:
On 01/27/2016 10:51 AM, Jay Pipes wrote:
On 01/27/2016 12:53 PM, gordon chung wrote:
It makes for a crappy user experience. Crappier than the crappy user
experience that OpenStack API users already have because we have done a
crappy job shepherdi
The HPE Helion Public Cloud is one of several OpenStack public clouds that
generously donate compute, network, and storage resources to power the
OpenStack Developer Infrastructure. As you may know, HPE is sunsetting the
HPE Helion Public Cloud on January 31st 2016[1]. Use of HPE Helion Public
Clou
On 27/01/16 11:02 -0800, Su Zhang wrote:
Hello everyone,
I created another BP for Newton release regarding glance community image
visibility based on Louis Taylor's original BP. I will continue working on
feature. Before I upload our implementation, it will be wonderful if anyone
in glance com
We should expand services_and_agents devref to describe how and why
configuration options should be segregated between services and agents. I
stumbled into this recently while trying to remove a confusing duplicate
configuration option [1][2][3]. The present separation appears to be
'tribal knowled
On 27/01/16 14:26 -0500, Cody A.W. Somerville wrote:
The HPE Helion Public Cloud is one of several OpenStack public clouds that
generously donate compute, network, and storage resources to power the
OpenStack Developer Infrastructure. As you may know, HPE is sunsetting the HPE
Helion Public Cloud
hi all,
there have been a few reviews recently where the issue of service type
versus project name have come up for use in the headers. as usual this
conversation can get quite murky as there are several good examples
where service type alone is not sufficient (for example if a service
expose
On Wed, Jan 27, 2016 at 7:06 PM, Flavio Percoco wrote:
>
> FWIW, the current governance model does not prevent competition. That's
> not to
> be understood as we encourage it but rather than there could be services
> with
> some level of overlap that are still worth being separate.
>
> What Jay is
Hi,
I would like to ask to be removed from the core reviewers team on the
Puppet for OpenStack project.
My day to day tasks and focus no longer revolve solely around Puppet and
I lack dedicated time to contribute to the project.
In the past months, I stopped actively reviewing changes compared t
Hi Sam,
After our conversation, I have few questions and consideration about Ekko,
mainly on how it works et similar. Also to make available to the community
our discussions:
- In understand you are placing a backup-agent on the compute node
and execute actions interacting directly with
Mathieu,
Thank you for all the work you've done over the past few years in this
community. You've done a lot and also done a lot to help answer questions
and mentor new folks.
On Wed, Jan 27, 2016 at 1:13 PM, Mathieu Gagné wrote:
> Hi,
>
> I would like to ask to be removed from the core reviewe
On Wed, Jan 27, 2016 at 1:47 PM, michael mccune wrote:
> i am not convinced that we would ever need to have a standard on how these
> names are chosen for the header values, or if we would even need to have
> header names that could be deduced. for me, it would be much better for the
> projects u
On 01/27/2016 03:13 PM, Mathieu Gagné wrote:
> Hi,
>
> I would like to ask to be removed from the core reviewers team on the
> Puppet for OpenStack project.
>
> My day to day tasks and focus no longer revolve solely around Puppet and
> I lack dedicated time to contribute to the project.
>
> In
On 01/27/2016 03:31 PM, Dean Troyer wrote:
On Wed, Jan 27, 2016 at 1:47 PM, michael mccune mailto:[email protected]>> wrote:
i am not convinced that we would ever need to have a standard on how
these names are chosen for the header values, or if we would even
need to have header names
Hi,
Puppet OpenStack Integration jobs [1] have been here for some months.
It seems like they're pretty stable when rubygems or EPEL is not down ;-)
I'm sure it will fail from time to time, like other jobs but 'recheck'
will do the job if we need to kick-off another run.
We might want to enable t
Hi Flavio,
On Wed, Jan 27, 2016 at 4:50 AM, Flavio Percoco wrote:
> [snip]
> However, as a community, I think we should send a clear message and protect
> our users and, in this case, the best way
> is to avoid adding this format as supported.
>
To address some of the concerns i have added a se
Hello,
I am looking at this blueprint
https://blueprints.launchpad.net/app-catalog/+spec/add-tosca-assets and
confused about the first task, "define metadata for TOSCA assets"? Can
someone please provide example of metadata for previous work on Heat and
Murano? I tried to find some old patch
- Original Message -
> From: "Sahdev P Zala"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> Hello,
>
> I am looking at this blueprint
> https://blueprints.launchpad.net/app-catalog/+spec/add-tosca-assets and
> confused about the first task, "define metadata
Hi,
I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661
We have radvd processes that the l3 agent launches, and if the l3 agent
is terminated these radvd processes continue to run. I think we should
probably terminate them when the l3 agent is terminated, like if we are
in
On Wed, Jan 27, 2016 at 12:35 PM, Emilien Macchi wrote:
>
>
> On 01/27/2016 03:13 PM, Mathieu Gagné wrote:
> > Hi,
> >
> > I would like to ask to be removed from the core reviewers team on the
> > Puppet for OpenStack project.
> >
> > My day to day tasks and focus no longer revolve solely around
On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins wrote:
> Hi,
>
> I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661
>
> We have radvd processes that the l3 agent launches, and if the l3 agent
> is terminated these radvd processes continue to run. I think we should
> probab
On Wed, 2016-01-27 at 16:21 +, Derek Higgins wrote:
> Hi All,
>
> We briefly discussed feature tracking in this weeks tripleo meeting.
> I
> would like to provide a way for downstream consumers (and ourselves)
> to
> track new features as they get implemented. The main things that
> came
>
Jamie
At the Nova mid-cycle and John Garbutt suggested I reach out to you
again to progress this issue.
Thanks
On 05/01/16 10:05, Carlton, Paul (Cloud Services) wrote:
Jamie
John Garbutt suggested I follow up this issue with you. I understand
you may be leading the
effort to address the is
On Wed, Jan 27, 2016 at 04:24:00PM EST, Assaf Muller wrote:
> On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins wrote:
> > Hi,
> >
> > I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661
> >
> > We have radvd processes that the l3 agent launches, and if the l3 agent
> > is te
On Tue, Jan 26, 2016 at 7:15 PM, Derek Higgins wrote:
> Hi All,
>
> For the last few months we've been alerting the #tripleo irc channel when
> a card is open on the tripleo trello org, in the urgent list.
>
> When used I think it served a good purpose to alert people to the fact
> that deploying
Hello Gyorgy,
Few more responses inline:
On 01/27/2016 02:51 AM, Gyorgy Szombathelyi wrote:
>>
>> Hi Gyorgy,
>>
> Hi Kevin,
>
>> I'll definitely give this a look and thanks for sharing. I would like to ask
>> however why you found OpenStack-Anisble overly complex so much so that
>> you've taken o
On Wed, Jan 27, 2016 at 4:52 PM, Sean M. Collins wrote:
> On Wed, Jan 27, 2016 at 04:24:00PM EST, Assaf Muller wrote:
>> On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins wrote:
>> > Hi,
>> >
>> > I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661
>> >
>> > We have radvd pr
1 - 100 of 125 matches
Mail list logo