Hi All,
+1 for Kairat. He has really done a lot of work both in reviews and commits.
Personally say, he helped me a lot with my patches as well. Thanks!
+1 for Brian. As I know, he has done great job in glance-specs review,
especially the image-import-refactor which is the most important goal
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 integrated (of course the
Hey Jay!
Thanks for the clarification. There was another thing that I wanted to
know, is there any provision to pass extra arguments or some extra
specifications along with the VM request to nova. To give you some context,
I wanted to pass a host:vm mapping to the nova scheduler for its host
selec
On 01/27/2016 06:20 AM, Ian Cordasco wrote:
>> In which way what you're proposing above is different from what we
>> currently have (ie: beta 1, 2 and 3)?
>
> we'd be communicating more strenuously to consumers that this was
> really meant to be a release that would be a very very very smooth
> up
On Jan 25, 2016, at 17:57, melanie witt wrote:
> Thanks!! That's indeed the same problem and removing the '$' from the
> exclude_regex worked for me. (ostestr --blacklist_file tests-py3.txt --regex
> "nova.tests.unit.network" ran all non-blacklisted network tests)
Argh, I spoke too soon, remov
Louis,
Just updated the etherpad. We planning from 9AM PST - 5PM PST.
- Sridhar
On Tue, Jan 26, 2016 at 12:35 PM, Henry Fourie
wrote:
> Sridhar,
>
>What time will the Tacker mid-cycle meeting start/end?
>
> -Louis
>
>
>
> *From:* Sridhar Ramaswamy [mailto:sric...@gmail.com]
> *Sent
hi,
thank you.
i guess this should be documented explicitly.
i submitted api-site patch: https://review.openstack.org/#/c/272882/
On Wed, Jan 27, 2016 at 3:01 AM, Sridar Kandaswamy (skandasw)
wrote:
> Hi Takashi:
>
> There were discussions around this sometime in the H cycle w.r.t the
> referenc
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 the actual
functionality). From a production stand point I think its safe to say we can
keep supporting the V1 implementation for a while however we'll
On 26 Jan 2016 13:30, "Liping Mao (limao)" wrote:
>
> Hi Gal,
>
> Thanks for your answer.
>
> >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)
>
>
Hi,
We’re scheduling interviews with application developers to help us understand
their processes around developing, testing and deploying apps to the cloud.
These are not folks that administer the cloud, but rather individuals that
consumer cloud services. The interviews take about 45 minutes
Hi Sridhar,
If we use Heat to create flavor and network, we may end up having multiple
flavors and networks(which are of same)for a VNFD.
RegardsBharath T
Date: Tue, 26 Jan 2016 11:22:34 -0800
From: sric...@gmail.com
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [tacker]Automa
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 master is currently broken, but it hasn't been used as
much as
Hi, Yipei,
have you installed two nodes devstack successfully or not? This error is
occurred during or after the installation?
If you have installed them successfully, then Volume type is not supported in
Cinder-apigw yet (you can help to implement it ☺ ). You can use –os-region-name
Pod2 para
As I recall, network_device_mtu sets up the MTU on a bunch of structures
independently of whatever the correct value is. It was a bit of a
workaround back in the day and is still a bit of a workaround now. I'd
sooner we actually fix up the new mechanism (which is kind of hard to do
when the close
Hi,
Before creating a new puppy in our forge, I would like to know if
somebody already deployed OpenStack Octavia [1] with Puppet.
We would like to have a module which would do this work in our OpenStack
forge [2].
Feel free to raise your hand otherwise we will work on it during the
next weeks.
Thats very very unfortunate. :/ Lbaas team, (or any other team), please never
do this again. :/
so does liberty/mitaka at least support using the old v1? it would be nice to
have a different flag day to upgrade the load balancers then the upgrade day to
get from kilo to release next...
Any ch
On 01/26/2016 05:05 PM, Matt Fischer wrote:
> Also +1 for ceph
>
> And Fernet is a great idea, Keystone is moving towards a day where it's
> default.
This is an etherpad in which we can brainstorm of the scenarios we want
to test:
https://etherpad.openstack.org/p/puppet-openstack-integration-sc
Yes, there is no information in the logs as Stanislaw said before, also
maybe exist another problem with syslog logging, so maybe on of the
solution is don't use -s option or external 'logger' program, and better
use simple redirection of stdout and stderr to the plain log file?
On Wed, Jan 27, 2
On Tue, Jan 26, 2016 at 9:57 PM, Jay Pipes wrote:
>
> I am not suggesting you "share an API" at all. I am requesting that if you
> have a RESTful API planned for your "backup", then you do not use the same
> RESTful API resource endpoint names that Freezer does. Because if you do,
> then users of
-Original Message-
From: Thomas Goirand
Reply: OpenStack Development Mailing List (not for usage questions)
Date: January 26, 2016 at 12:48:09
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating o
I get this when running tempest now on a devstack I installed today. I did
not have this issue on a devstack installation I did a few days ago. This
is on ubuntu 14.04 LTS.
Everything else on this system seems to be working just fine. Only
run_tempest throws this exception.
./run_tempest.sh -s;
+1!
Well deserved!
Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis
On Tue, Jan 26, 2016 at 5:20 AM, Yang, Lin A wrote:
> Glad to see this happened. :)
> Well deserved, Victor.
>
> Lin Yang
> @Intel
>
>> On Jan 23, 2016, at 01:33, Serg Melikyan wrote:
>>
>> I would like to no
Also +1 for ceph
And Fernet is a great idea, Keystone is moving towards a day where it's
default.
On Tue, Jan 26, 2016 at 2:20 PM, David Moreau Simard wrote:
> +1 for adding puppet-ceph and Ceph integration in Nova, Cinder and Glance.
>
> This means there would be two scenarios involving Cinder
I have seen this twice now. Once on a devstack I downloaded a few days ago,
and again today. What I discovered was that if I reboot the machine, the
credentials for rabbit go back to the defaults. The symptom is anything
that requires any sort of authentication results in a 500 nova list,
neu
On 01/26/2016 03:28 PM, Sam Yaple wrote:
On Tue, Jan 26, 2016 at 10:15 AM, Jay Pipes mailto:jaypi...@gmail.com>> wrote:
On 01/26/2016 02:47 AM, Sam Yaple wrote:
Hello Fausto,
I am happy to have a conversation about this with you and the
Freezer
team. I have
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
> this into its log. In our case there are just no log - ntpdate send first
> packet, get an answer - that's all. So, fudging won't save us, as I think.
> Also,
Hi,
As Brandon pointed out you can’t run V1 and V2 at the same time because they
share the same database tables and interpret columns differently. Hence, at HPE
we have some proprietary script which takes the V1 database tables and migrates
them to the V2 format. After that the v2 agent based d
-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 is still space :)
Thanks.
My recent code revie
+1 for adding puppet-ceph and Ceph integration in Nova, Cinder and Glance.
This means there would be two scenarios involving Cinder (lvm+iscsi and
RBD) and three scenarios involving Glance (file, RBD, Swift)
I find it redundant to install components in the same way across all three
scenarios. Per
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
.
On Tue, Jan 26, 2016 at 1:54 PM, Bogdan Dobrelya
wrote:
> We are going to switch [0] to external astute
When there is too high strata, ntpdate can understand this and always write
this into its log. In our case there are just no log - ntpdate send first
packet, get an answer - that's all. So, fudging won't save us, as I think.
Also, it's a really bad approach to fudge a server which doesn't have a
re
I assumed they couldn't run on the same host, but would work on different
hosts. maybe I was wrong?
I've got a production cloud that's heavily using v1. Having a flag day where we
upgrade all from v1 to v2 might be possible, but will be quite painful. If they
can be made to co'exist, that would
Really? This is going to cause me a major headache if true. Brandon, do you
have any details?
Thanks,
Kevin
From: Major Hayden [ma...@mhtx.net]
Sent: Tuesday, January 26, 2016 12:07 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [ope
Sridhar,
What time will the Tacker mid-cycle meeting start/end?
-Louis
From: Sridhar Ramaswamy [mailto:sric...@gmail.com]
Sent: Tuesday, January 26, 2016 11:11 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tacker] No weekly IRC meeting ne
Oh lbaas versioning was a big deal in the beginning. Versioning an
advanced service is a whole other topic and exposed many "interesting"
issues with the neutron extension and service plugin framework.
The reason v1 and v2 cannot be run together are mainly to get over an
issue we had with the 2 d
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
vacation
when it was firs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/26/2016 02:01 PM, Fox, Kevin M wrote:
> I believe lbaas v1 and v2 are different then every other openstack api
> version in that while you can run v1 and v2 at the same time but they are
> completely different systems that just share a name.
I believe lbaas v1 and v2 are different then every other openstack api version
in that while you can run v1 and v2 at the same time but they are completely
different systems that just share a name. A lb created in v1 doesn't show up in
v2 or vis a versa. But being able to enable both at once giv
Hi Kevin,
On Tue, 2016-01-26 at 19:48 +, Kevin Carter wrote:
> Seems like a sensible change however I'd love to see it written up as a spec.
> Also do we know if there are any scenario tests in tempest for octavia or
> would we need to develop them/something?
There aren't any tempest tests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/26/2016 01:48 PM, Kevin Carter wrote:
> Seems like a sensible change however I'd love to see it written up as a spec.
> Also do we know if there are any scenario tests in tempest for octavia or
> would we need to develop them/something?
>
>
Hi Jay, Dean,
totally agree, with Sam, we'll make sure there will not be any overlap.
Sam,
Thanks for your openness. I'd like to have a conversation about it. When
you say "current direction of Ekko will add many components" do you have
any reference, plan or road map where we can see that directi
Seems like a sensible change however I'd love to see it written up as a spec.
Also do we know if there are any scenario tests in tempest for octavia or would
we need to develop them/something?
As for adding Octavia as a new service within OpenStack Ansible this makes
sense. Another approach ma
On Tue, Jan 26, 2016 at 11:42 AM, Stanislaw Bogatkin
wrote:
> Hi guys,
>
> for some time we have a bug [0] with ntpdate. It doesn't reproduced 100% of
> time, but breaks our BVT and swarm tests. There is no exact point where
> problem root located. To better understand this, some verbosity to ntpd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey there,
After poking around a bit at LBaaS in OpenStack-Ansible, I discovered that
LBaaS v2[1] was available in Liberty and Mitaka. At first, I thought it
involved switching agents from neutron-lbaas-agent to neutron-lbaasv2-agent,
but things
big +1 from me. :)
Kevin
From: Sean M. Collins [s...@coreitpro.com]
Sent: Tuesday, January 26, 2016 9:59 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] MTU configuration pain
On Mon, Jan 25, 2016
Hi Bharath,
As further discussed in today's IRC meeting [1], the image creation
proposal you laid out seems a reasonable near term approach.
It also doesn't preclude future enhancements to do image-download during
VNFD on-boarding (image pre-positiong in a multi-site scenario). In that
case VNFD
As discussed in today's irc meeting, we are skipping next weekly meeting
scheduled for Tuesday Feb 2nd [1] as we already have a 2-day mid-cycle
meetup [2] later this week.
- Sridhar
[1] https://wiki.openstack.org/wiki/Meetings/Tacker
[2] https://etherpad.openstack.org/p/tacker-mitaka-midcycle
___
On 01/21/2016 02:38 AM, Ian Cordasco wrote:
> That said, I'd like to see a different release cadence for cycles that are
> "stabilization cycles". We, as a community, are not using minor version
> numbers. During a stabilization cycle, I would like to see master be
> released around the 3 milestone
Hi guys,
for some time we have a bug [0] with ntpdate. It doesn't reproduced 100% of
time, but breaks our BVT and swarm tests. There is no exact point where
problem root located. To better understand this, some verbosity to ntpdate
output was added but in logs we can see only that packet exchange
Hi there,
Michał is correct, it should be saved.
Do u have a small example of what u are trying to do because that will
help determine if what u are doing will be saved or whether it will not be.
Or even possibly explaining what is being done would be fine to (more
data/info for me to reason
Hi Gyorgy,
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 ran into and see what w
Hi Takashi:
There were discussions around this sometime in the H cycle w.r.t the
reference implementation. IIRC, the consensus was that if a Firewall is
configured, the points of insertion should be conservative and drop all
traffic when admin_state_up is False. Only removing the Firewall will pas
On Mon, Jan 25, 2016 at 08:16:03PM EST, Fox, Kevin M wrote:
> Another place to look...
> I've had to use network_device_mtu=9000 in nova's config as well to get mtu's
> working smoothly.
>
I'll have to read the code on the Nova side and familiarize myself, but
this sounds like a case of DRY that
On 1/26/16, 8:35 AM, "Michał Dulko" wrote:
>On 01/26/2016 10:11 AM, Michał Jastrzębski wrote:
>> Well we still can perform upgrades with some API downtime, so it's not
>> like we're bound to rolling upgrades on architectural level. I'll talk
>> to you after midcycle and we'll find a good way to
On Tue, Jan 26, 2016 at 10:01:56AM -0600, 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
Didn't hit the mailing list with the last reply. Forwarding to a wider
audience than just Dean
-- Forwarded message --
From: "Sam Yaple"
Date: Jan 26, 2016 12:00 PM
Subject: Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup
for OpenStack
To: "Dean Troyer"
Cc:
On
Hi folks,
Puppet OpenStack integration jobs [1] are very helpful to perform
functional testing when deploying OpenStack with our modules.
We current run scenario 001 and 002 on both centos7 & trusty, which is 4
jobs in the check queue.
I would like to propose some changes, feel free to comment:
A reminder,
Since M-2 milestone has now passed (Mitaka-2, January 21st), your third
party CI driver testing system should have completed the following:
"Mitaka-2 milestone: Driver teams will have registered their intent to run
CI by creating system accounts and identifying a point of contact for
Hi,
Sounds like a bug. I think we should prohibit adding duplicate links on
nailgun side, using link title + link url as a key.
I've created a bug: https://bugs.launchpad.net/fuel/+bug/1538209. I hope it
will be fixed by the HCF so that the fix will be included in 8.0.
2016-01-26 19:23 GMT+03:00
On Tue, Jan 26, 2016 at 9:28 AM, Sam Yaple wrote:
> On Tue, Jan 26, 2016 at 10:15 AM, Jay Pipes wrote:
>
>> My personal request is that the two contributor communities do everything
>> in their power to ensure that the REST API endpoints are not overlapping.
>> The last thing we need is to have
Hi all,
In the scope of the LMA plugins, we've played with the new ability to
insert links in the Fuel dashboard. This works fine from the UI standpoint
except that to avoid creating duplicate links we've come up with a solution
that is intricate and brittle IMO.
Basically we have an exec resource
The log of this IRC meeting can be found here:
http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-01-26-15.03.log.html
Best,
Mohammad
From: Mohammad Banikazemi/Watson/IBM@IBMUS
To: "OpenStack Development Mailing List \(not for usage questions
\)"
Date: 01/25/2
Ihar's e-mail summarizes things quite nicely. We have an ongoing topic
of conversation[1] about MTU configuration in Neutron. It is my personal
viewpoint that the current Neutron configuration for MTUs is not
intuitive and can be improved. There are a number of options that you
had to enable in the
-Original Message-
From: Kuvaja, Erno
Reply: OpenStack Development Mailing List (not for usage questions)
Date: January 26, 2016 at 09:00:30
To: Flavio Percoco , OpenStack Development Mailing List (not
for usage questions)
Subject: Re: [openstack-dev] [glance] Glance Core team addi
On Tue, Jan 26, 2016 at 10:46 AM, Dan Prince wrote:
> On Mon, 2016-01-25 at 15:08 -0500, James Slagle wrote:
> >
> >
> > On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince
> > wrote:
> > >
> > > As for tripleo-heat-templates... sure it hasn't been an entirely
> > > smooth
> > > ride. I think a lot of t
We are overjoyed to announce the release of:
oslo.config 3.4.0: Oslo Configuration API
This release is part of the mitaka release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.config
With package available at:
https://pypi.python.org/pypi/oslo.config
On Mon, Jan 25, 2016 at 11:44 AM, Sean M. Collins
wrote:
> Just an FYI for anyone taking the Neutron piece, please feel free to
> attend the upgrades subteam - we have a meeting today.
>
> https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam
> --
> Sean M. Collins
>
Thanks Sean. I j
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 in on this yet, in part because I was on vacation
whe
On Tue, 2016-01-26 at 09:23 -0500, Tzu-Mainn Chen wrote:
> - Original Message -
> > 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
On Mon, 2016-01-25 at 15:08 -0500, James Slagle wrote:
>
>
> On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince
> wrote:
> >
> > As for tripleo-heat-templates... sure it hasn't been an entirely
> > smooth
> > ride. I think a lot of the pain has to do with a lack of CI
> > coverage on
> > proper upgra
On Tue, Jan 26, 2016 at 10:27 AM, Dan Prince wrote:
> On Tue, 2016-01-26 at 09:56 -0500, James Slagle wrote:
> >
> >
> > On Tue, Jan 26, 2016 at 9:08 AM, Steven Hardy
> > wrote:
> > > On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote:
> > > >On Tue, Jan 26, 2016 at 4:46 AM, Steven
- Original Message -
> On Tue, Jan 26, 2016 at 09:23:00AM -0500, Tzu-Mainn Chen wrote:
> > - Original Message -
> > > 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, Be
On 01/26/2016 10:23 AM, pn kk wrote:
> Hi,
>
> I use taskflow for job management and now trying to persist the state
> of flows/tasks in mysql to recover incase of process crashes.
>
> I could see the state and the task results stored in the database.
>
> Now I am looking for some way to store the
On 01/26/2016 10:11 AM, Michał Jastrzębski wrote:
> Well we still can perform upgrades with some API downtime, so it's not
> like we're bound to rolling upgrades on architectural level. I'll talk
> to you after midcycle and we'll find a good way to tackle it.
Sure, this will work. projects.yaml sa
Hi,
I use taskflow for job management and now trying to persist the state of
flows/tasks in mysql to recover incase of process crashes.
I could see the state and the task results stored in the database.
Now I am looking for some way to store the input parameters of the tasks.
Please share your
On Tue, Jan 26, 2016 at 10:15 AM, Jay Pipes wrote:
> On 01/26/2016 02:47 AM, Sam Yaple wrote:
>
>> Hello Fausto,
>>
>> I am happy to have a conversation about this with you and the Freezer
>> team. I have a feeling the current direction of Ekko will add many
>> components that will not be needed
On Tue, 2016-01-26 at 09:56 -0500, James Slagle wrote:
>
>
> On Tue, Jan 26, 2016 at 9:08 AM, Steven Hardy
> wrote:
> > On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote:
> > > On Tue, Jan 26, 2016 at 4:46 AM, Steven Hardy > om> wrote:
> > >
> > > On Mon, Jan 25, 2016 at 05:4
Well we still can perform upgrades with some API downtime, so it's not
like we're bound to rolling upgrades on architectural level. I'll talk
to you after midcycle and we'll find a good way to tackle it.
Cheers,
Michal
On 26 January 2016 at 08:40, Michał Dulko wrote:
> On 01/23/2016 02:32 AM, St
On Tue, Jan 26, 2016 at 09:23:00AM -0500, Tzu-Mainn Chen wrote:
> - Original Message -
> > 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 we
Hi Takashi,
At least in Liberty, with the reference iptables firewall, it looks like
setting the admin state of the firewall to DOWN results in traffic hitting only
the neutron-l3-agent-fwaas-defau chain. The action there is to DROP all traffic.
James
On 1/26/16, 4:15 AM, "Takashi Yamamo
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: 26 January 2016 14:42
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [glance] Glance Core team additions/removals
>
>
> Greetings,
>
> I'd like us to have one more core cleanup for this cyc
On Tue, Jan 26, 2016 at 9:08 AM, Steven Hardy wrote:
> On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote:
> >On Tue, Jan 26, 2016 at 4: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 Har
On 21/01/16 12:10 -0430, Flavio Percoco wrote:
On 20/01/16 13:16 -0430, Flavio Percoco wrote:
Yo! Glancers,
Gonna cut the chase: I think we would do a better job on the specs (and light
specs) side if we get rid of the Glance Drivers team and encourage everyone
(especially from the core team) t
Greetings,
I'd like us to have one more core cleanup for this cycle:
Additions:
- Kairat Kushaev
- Brian Rosmaita
Both have done amazing reviews either on specs or code and I think they both
would be an awesome addition to the Glance team.
Removals:
- Alexander Tivelkov
- Fei Long Wang
Fei
On 01/23/2016 02:32 AM, Steven Dake (stdake) wrote:
> Hello,
>
> In our weekly IRC meeting, all developers and others in attendance
> were in unanimous agreement that upgrades are the #1 priority for
> Kolla to solve [1]. inc0 has developed both a simple database
> migration implementation around
- Original Message -
> 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 in on this yet, in part because I was on vacation
> > >> when it was
Hi Tackers,
I have uploaded a new patchset for the automatic resource creation spec[1]. I
haven't addressed some comments and as I am unable to attend to mitaka midcycle
meetup, I am sharing below few thoughts on this spec.
Image Creation:
In the latest patchset, image creation at the time
On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote:
>On Tue, Jan 26, 2016 at 4: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
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 Neutron devstack grenade jobs and what your work has
uncovered on the Neutron side that might be possib
Hi Igor,
Thank you for question!
I will try to explain why we want to add functionality for building deb/rpm
packages.
* We want to cover the whole workflow: from building a package till adding that
package into the new or existing repository.
* We want to consolidate all knowledge about manag
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
instances was offloaded to be able to spawn new instances or to
unshelv
Hi Zhiyuan,
Your solution works, but I encountered another error. When executing
command
"openstack volume type create --property volume_backend_name=lvmdriver-1
lvmdriver-1",
it returns
"Unable to establish connection to
http://192.168.56.101:19997/v2/c4f6ad92427b49f9a59810e88fbe4c11/types";.
On Tue, Jan 26, 2016 at 4: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 in on this yet, in part because I was on v
Hi Tan,
While the cross project spec was discussed Glance already had implementation of
request ids in place. At the time of the Glance implementation we assumed that
one request id is desired through the chain of services and we implemented the
req id to be accepted as part of the request. Thi
Hi Sahara folks!
I want to bring your attention to the problem that described in this bug:
https://bugs.launchpad.net/python-saharaclient/+bug/1534050 It was raised
on the previous irc-meeting, but we didn't come to a conclusion.
One of the ways to fix it is not-None sentinel object that will be
On 01/14/2016 12:54 PM, Steven Hardy wrote:
On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote:
Hey all,
I realize now from the title of the other TripleO/Mistral thread [1] that
the discussion there may have gotten confused. I think using Mistral for
TripleO processes that are obv
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.
We also have a new meeting channel which is #openstack-meeting-cp where the
cross-project meeting will now take place at it's usual time Tuesd
Armando M. wrote:
On 20 January 2016 at 08:20, Edgar Magana wrote:
Just providing support for Kyle’s proposal!
It is working very well for other teams such as nova, docs between others.
At risk of stating the obvious, not every project is equal, and as I
mentioned in an earlier response,
We are going to switch [0] to external astute.yaml fixtures for Noop
tests and remove them from the fuel-library repo as well.
Please make sure all new changes to astute.yaml fixtures will be
submitted now to the new location. Related mail thread [1].
[0]
https://review.openstack.org/#/c/272480/1/
Thanks for investigating the tabulate option :-)
Victor
Le 26/01/2016 02:25, Joshua Harlow a écrit :
As far as the other option (using tabulate):
https://bitbucket.org/astanin/python-tabulate/pull-requests/25/
That was a (very very basic) POC for a potential compatibility layer,
The author (
1 - 100 of 122 matches
Mail list logo
